A curious case of lifting state in React
5d 21h ago in programming@programming.dev from 01def.ioMaybe Lemmy can forcibly invent a new term for "ricing". (Good faith pls)
1y 5mon ago in linux@lemmy.ml from discuss.tchncs.deEnterprise misery
1y 5mon ago in linuxmemes- Struggle to come to a conclusion on what to do with the EOL OS because of internal political factors and the reality of how enterprise works.
This is the involuntary choice. If you cannot choose from the first three, you end up implicitly choosing the fourth.
I understand how it feels.
The only way that will work is to somehow quit and rejoin as a much more highly paid consultant and enable them to upgrade EOL software in prod. I am actually considering this.
There is something you need to know about collective wisdom; the larger the org is, the lower it gets. Yes the application works on Alma 8 and 9, but the management says 'no'.
Any large enterprise still running RHEL 5 in Prod (or even, yes, older RHEL versions) has fully accepted the risks
It is more like 'involuntarily end up riding the risks of using unsupported old software'. RHEL 7 and RHEL 5 are in the right order.
RHEL sells an unrealistic expectation that you don't need to worry about the OS for another 10 years, so the enterprise gets designed around it and becomes unable to handle an OS upgrade, ever.
I am not. I worked hard to make our application support RHEL 8 and then RHEL 9. And then the politics takes over and the big wigs start an extended bickering over who should pay for the OS upgrade... which never happens. Sometimes hardware partners don't support the upgrades, which means OS upgrades also end up requiring new hardware.
I blame Redhat.
...hope...
Permanently Deleted
1y 5mon ago in linux@lemmy.mlCheck if there's any large file in /tmp and /run/user/*?
I think Deno made a huge mistake. (Node compatibility)
1y 5mon ago in programming@programming.devThere is no way legacy projects are going to switch to Deno. Even when Deno is 100% compatible, the only advantage Deno provides is slightly higher performance.
Node's complexity problem? All those configs needs to be supported for compatibility anyway. Typescript? The project already has tsconfig.json set up, so they might as well continue to use tsx. Security? I bet users will just get tired and use -A all the time.
To benefit from Deno, Node's legacy needs to be shed.
Wine is a different case. The reason Wine makes sense is because Windows is so much worse than Linux that even with scrappy game compatibility, Linux offers a better experience. For Linux users, the alternative to Wine is not switching to Windows, it is not being able to play games. On the other hand, legacy Node projects have a very easy alternative... just continue to use Node.
And btw Bun is making the same mistake.
I made a library similar to Testcontainers, but works differently.
1y 7mon ago in programming@programming.dev from github.comSelf terminating container images for real world dependencies to support your unit tests
1y 10mon ago in programming@programming.dev from gitlab.comI got average monthly ratings for games on Wine AppDB, and seems like something happened in 2016.
1y 10mon ago in linux@lemmy.mlGive your JS codebase what it deserves!
1y 10mon ago in programmer_humor@programming.dev from github.comTesting a routing protocol using network namespaces
2y 23d ago in programming@programming.dev from 01def.ioHow exactly does linux use prefix length assigned to network interface?
2y 4mon ago in linux@lemmy.mlAnyone else wants a one box replacement to a switch attached to USB NICs?
2y 8mon ago in selfhosted





