421–430 of 481 posts
I don't understand who uses that network anymore. Everytime I login it's all ai generated stories next to ai generated flavor images of people sounding like a parody of themselves ("what taking my kids to school taught me about business scaling"). Out of all places to doomscroll, why choose the one that feels like an episode of Severance?
Earlier quoted context omitted.
I got my last job there, and I have a steady queue of recruiters reaching out the whole time. So I will probably continue to use it as long as I need to eat. I don't engage with the feed at all though. I believe the same applies to many others as well
I've also gotten my last few jobs there. It's great for that. Even if it's 90% low effort recruiter spam. It's also full of "greatest team in the world", pizza parties, "incredible" training sessions, and "meetings of great minds". And now it's turned into a bunch of comedy reels. Blah.
The fact that they hijack scrolling to artificially limit scroll speed is insane to me. Feels like I'm trying to navigate through molasses
Scroll down through jobs, hit next page. Page reloads at bottom of list on next page. Have to scroll up then scroll down, every page. Baffles me ui like this exists in 2026.
Back in the ancient days of the web, browsers allowed you to set resource limits (ram, cache, etc) to prevent websites from hogging the limited resources of your desktop system. It's really a shame that all major browsers have since decided that you as a user should have almost no control over how much ram and storage any arbitrary website can consume now.
Goes with the territory of allowing remote code execution arbitrarily and all the time otherwise you won't be able to.. * checks notes * read text on the internet.
B—b-it 4K scaling! Reactive design (to read text)! Emojis, reactions, badges! Memes and gifs!
Let's be real, LinkedIn is full of LinkedIn Lunatics but pretty much all mainstream social media is pretty shit. They're just different flavors of shit. LinkedIn: bad. Facebook: bad. Twitter: I literally think it contributed to the collapse of discourse and rise of shallow thought / rejection of expertise. I'm not going to list more because the theme is, you guessed it, they're bad. Google+ had promise in that the ma…
hackernews has a good signal to noise ratio, noise is bad
Earlier quoted context omitted.
I got my last job there, and I have a steady queue of recruiters reaching out the whole time. So I will probably continue to use it as long as I need to eat. I don't engage with the feed at all though. I believe the same applies to many others as well
I've also gotten my last few jobs there. It's great for that. Even if it's 90% low effort recruiter spam. It's also full of "greatest team in the world", pizza parties, "incredible" training sessions, and "meetings of great minds". And now it's turned into a bunch of comedy reels. Blah.
Earlier quoted context omitted.
I got my last job there, and I have a steady queue of recruiters reaching out the whole time. So I will probably continue to use it as long as I need to eat. I don't engage with the feed at all though. I believe the same applies to many others as well
Beeper has LinkedIn integration, so you can chat with recruiters with any Matrix app without ever opening the website. https://www.beeper.com/
This is the part about the "wasm won't replace JavaScript" argument I see being slept on and why I am so disheartened about how practically no progress has been made on it. Most trivial apps don't need to be optimized, and for them, JavaScript is fine. But for complex interactive web applications - it really fuggin matters. Think; - vscode - facebook - jira - linkedin - reddit There's no reason these applications sho…
I realize this is not an orthodox view, but WASM won't make the typical user have a better experience. I think it could improve Photopea, the various office suite programs, and perhaps unknown unknowns. But, much more important than the uncertain is the current Web which will become less accessible and closed. The ease in reverse engineering JavaScript has more than once shown negligence and malice by Website develop…
The first thing to highlight is that multithreading is possible but extremely impractical on the web, and even if you succeed, it's slow. Check out Surma's video on it: https://www.youtube.com/watch?v=7Rrv9qFMWNM
Using threads unlocks so much performance, from everything to time-to-first-paint, time-to-interactive all the way to the general feel of the application.
That sort of optimization is trivial in languages designed for it (like Rust or Go).
Developer experience on the web is unbelievably poor. TypeScript is, semantically, fantastic, but then you have to build it - do you use swc or tsc, do you use webpack, rollup, rspack, vercel's stack, etc? Once you build it, what are your transpilation targets - did you even configure them or are you building bundles that are 40% larger for no reason? The runtime overhead of bundles is also non trivial.
Languages like Rust are maybe 20% more complicated than TypeScript - but they have TSX (also Vue templates, Angular templates, whatever) baked into the _core_ language - requiring no external transpilers or LSPs.
That doesn't mean every application is a good candidate for native/wasm - but the applications that would benefit would benefit end users and developers immensely.
The push back really makes no sense to me. Everyone complains about Electron (and OP about Linkedin, and everyone about Jira) being slow or eating up half their ram - yet with the same breath say that wasm would have no benefit.
> The ease in reverse engineering JavaScript
It's not as easy to reverse engineer native binaries - but you can do it pretty easily and produce the equivalent of minified source code from it. This is how emulators and custom firmware is created. It wouldn't prevent security researchers from identifying negligence.
Earlier quoted context omitted.
it's unironically just react lmao, virtually every popular react app has an insane number of accidental rerenders triggered by virtually everything, causing it to lag a lot
well that's any framework with vdom, the GC of web frameworks, so I'd imagine it's also a problem with vue etc.. I don't understand though why performance (I.e. using it properly) is not a consideration with these companies that are valued above $100 billion like, do these poor pitiful big tech companies only have the resources to do so when they hit the 2 trillion mark or something?
If you look at older desktop GUI frameworks designed in a performance-oriented era, none of them use the React paradigm, they use property binding. A good example of getting this right is JavaFX which lets you build up functional pipelines that map data to UI but in a way that ensures only what's genuinely changed gets recomputed. Dependencies between properties are tracked explicitly. It's very hard to put the UI into a loop.