This basically exists in Austria as “Altersteilzeit” [0] (“old age part time”). You even get 50% of your loss of income back through social security. So e.g. when reducing work by 40% you still get 80% of your salary. I’m guessing this is to incentivise employers to keep people near retirement employed as it would be much more expensive for the state to finance them if they were unemployed.
can you elaborate on the phone basis with engineers? I can’t really imagine how that wouldn’t be much more hassle discussing details without written documents, so I’m intrigued
The way NASA did it for decades was conference calls. Nowadays it's Teams meetings.
The outputs of the meetings are decisions that are later encoded in very many very long documents. It's just faster to hash out engineering details when the relevant engineers are able to talk to each other in real time and relevant decision makers are present to be able to unofficially bless or reject what the engineers come up with (formal acceptance of these decisions is of course a paperwork thing).
So, in this domain anyway, it's not a literal phone call. But it's what we see as the modern equivalent.
You do both, but I know at work for me the problem with written communication is we just talk past each other. Writing is, still, a very distilled and compressed medium. Meaning, a lot of the information is lost when translated to writing. I've spent weeks talking over email and on ticket just to solve it within 5 minutes on a zoom call.
A picture is worth a thousand words -- but only those to describe the picture. Hardly any sets of a thousand words can be adequately described with pictures.
I only visit social media in browser, I don't have any social media apps installed on my phone. Safari supports user scripts which I have installed on my phone.
we're definitely under heavy load right now - might be hitting some rate limits. can you try again now? if it still doesn't work, hit me up at dli@asim.sh or on our discord https://www.asim.sh/discord and i'll get you sorted!
I really like the approach but the demo [0] doesn’t really work on iOS Safari (although might be my outdated 16.7.8 version).
Scrolling doesn’t work, the layout and buttons have weird line breaks, the native search button is embedded in the custom designed one, leading to 2 icons…
The author is using a trick they've used in almost every past submission: They implement much less than the component they compare themselves to, and then show how much smaller their own solution is.
> Built with Vite, TypeScript, Tailwind, and Shadcn/UI, following the official ShadCN/Vite documentation exactly — no additions or removals.
Would be interesting to run Webpack Bundle Analyser [1] (or similar for vite bundler) to see if the proposed stack in the doc is bloated by some major dependencies.
Edit : seems the question I was responding for was a rhetoric question posted by the author. I guess the « smaller that a button » is a smart catchphrase but I wouldn’t use it for too long as soon a Nue becomes popular. Great work, I wish you much success and hope to use it in day to day work some time soon !
Does your button component implement all the functionality included in the Vite/shadcn bundle? E.g. the different variants, states, loading etc.?
I'm sorry if it does, then I'll take my accusation back, but I've seen this happen in almost all of your Nue submissions. People keep bringing up this criticism, and you never retract your misleading comparisons.
The Nue button demo isn’t claiming to replicate every feature of the Vite/ShadCN bundle—no variants, states, or loading spinners here, just a lean example to show size and simplicity. The point’s not to ‘beat’ ShadCN at its own game but to highlight how web standards can cut bloat dramatically, like a button smaller than a full SPA. I get the criticism—comparisons can feel loaded—but it’s less about misleading and more about spotlighting a different approach. Happy to tweak the framing if it’s coming off wrong.
> The point’s not to ‘beat’ ShadCN at its own game but to highlight how web standards can cut bloat dramatically, like a button smaller than a full SPA.
Then why isn't there any disclaimer or explanation that your Nue button has fewer features than the one you compare it to? You clearly intend for the reader to make this comparison, but you deceive them by not mentioning that your solution isn't equivalent.
> Happy to tweak the framing if it’s coming off wrong.
It would be great if you could do that! Though I'm not holding my breath - you've done this many times before, people have complained many times before, and you keep doing it.
I know I'm just one voice, but your marketing strategy is so deliberately deceitful that I'll honestly never consider Nue as a serious contender for any project, nor other software you write, until you stop doing this.
[0] https://www.oesterreich.gv.at/de/themen/arbeit_beruf_und_pen... (only in German unfortunately)