Really? Do you have links to any good analysis on this?
I'd be shocked, given that the bun team has shown a ton of maturity in all their messaging as far as API compatibility, engineering chops, and attention to detail. Nothing I've seen suggests that they'd be sloppy on the security side.
The issue list is full of bugs with segfaults. At least used to be when I last time checked it. But that is what you get with C/C++/Zig et all. It takes a lot of time to get good enough fuzzing and testing process to eliminate all that. In Chrome, for example, you could get $20,000 bounty just for demonstration of memory issue without an actual exploit.
"1 more step function in performance bro, V8 was cool but just 1 more and we'll have enough to make CRUD apps in JS, bro I promise"
Or you can use React Query/Tanstack Query, not waste cycles and bandwidth on RSC, get an app with better UX (http://ilovessr.com), and a simpler mental model that's easier to maintain.
Yeah Vite+Reat+Tanstack SPA apps is definitely the way to go for a majority of web apps. I would still stick with nextjs for ecommerce or pages that need to load instantly when clicked from google however.
> Think of it like WWII, only only instead of planting victory gardens to beat the Nazis, we're building AI apps and finding ways to create the economic value needed to cover the reckless bets being made by the elites.
LOL fuck this, the stock market deserves to burn to the ground.
While there are a lot of problems with the current market dynamics, burning it to the ground would cause a ridiculous amount of suffering. We need to spin up a new alternative then wind down the market gently.
I'm anti-establishment because the establishment doesn't care about anyone but themselves. What are we doing all this work for? Progress would be getting universal healthcare for all in this country. Getting better work life balance. Being able to afford a home. Now it's just all the "haves" fighting bitterly to keep getting more and more until they have everything and nothing for anyone else.
That's one negative quality that Hacker News always had to me, compared to older hacker spaces such as newsgroups and Slashdot: The Petit bourgeois conformism and materialism. People always drunk the Venture Capital pseudo-libertarian cool-aid with too much enthusiasm here.
Being anti-establishment should not be viewed as a sin, unless in extreme cases.
I have noticed that it coincides with the re-election of a certain political candidate (He who must not be named).
The facade of "critical and rational thinker" has all but completely fallen away and this place has revealed itself for the true ideological echo chamber that it is.
Since when are Hackers™ pro establishment? Also what's wrong with being anti-establishment exactly, especially the current one, or really most of the recent neoliberal ones?
The only problem is that the stock market is tied to a bunch of retirement/pension and other accounts. Yes stock market should burn to the ground but also I think pensioners and retirees shouldn’t be put out, just the finance bros and private equity folks which money is just a plaything.
This is pretty myopic, or something. Shows, at least, a real ignorance about the available possibilities (or lack thereof)—at scale—to the common worker for “saving for a later day”.
But I’m all ears. Now that you’ve diagnosed how 401K investing fools get what they deserve, care to offer any alternative solutions as to the entire work force should have been saving towards retirement.
(kinda unrelated but) I personally hate these forced savings schemes from the government. At least in my country the rates are low so it almost feels like I'm donating the entire difference in rates between the pension scheme and the S&P500 + taxes straight to the government.
At least give those of us brave (or stupid) enough to do something different with the money the option to.
I guess. My company (and I believe most) highly incentivize it by offering matching funds. The company says, "want to save $1000 of your paycheck? We'll throw in $500". The general wisdom is, you'd be an idiot to leave money like that going unreclaimed.
Where I am there's actually a %-age of your salary/wage that's "returned" to you when you retire. You don't get a choice.
You can choose to contribute to an employer-match scheme (I do) or even fund your own pension account with monthly payments to a pension provider. But these are in addition to the above forced pension.
Pension funds should be diversified and have a mix of asset classes that includes more than the stock market. Ideally, most of these assets will move independently so if one is doing particularly badly the others can balance it out to reduce overall volatility. If your pension fund is too heavily weighted to the market, that's a management problem with your fund.
I think HN is it's own anti-react bubble that really doesn't match reality. Everyone here decided they hated react in 2016 or whatever and doesn't want to update their worldview to the reality that react is frankly an amazing tool today.
Kind of sad to see a 2022 paper about svelete with extremely questionable benchmarks get upvoted so much vs all the great things that came out of react conf yesterday.
Have had our apps on expo for a while. Highly recommend, much easier upgrades and you can turn off any platform vendor stuff like their OTA updates and do local builds also. Expo + RN has saved us a ton of time on our apps and no way a small team like us could support both platforms otherwise.
Performance of WASM issues. Rendering performance of large data grids is not good. Also the first load time is also terrible 50mb+ payloads.
Blazor server uses websockets and is just a whole other bag of hurt. You'll have to deal with disconnects even if you can stomache the increased cloud costs.
50mb payloads are very extreme. There's definitely a few MB of hurt for WASM - but nextjs is just the same, plus it doesn't have the excuse of having to download the entire CLR!
You can (and I have) definitely rendered huge data grids efficiently with Blazor.
The biggest drawback with wasm is no proper multithreading support which has been delayed for years.
On blazor server; I totally agree, it's a pain. But for 'intranet' style apps which are used internally it's by far the most productive development environment I've used for web. I wouldn't use it for anything that wasn't a total MVP for public use but it's pretty great for internal apps like admin panels.
Blazor static server side + HTMX is probably the only way to make a cost efficient and performant version of Blazor suitable for public websites. WASM is way too big and slow, Websockets take up server resources and cause problems with timeouts where the user has to refresh their screen losing all state.
What would be the benefit over Razor pages tho ? Component model ? Feels like partial views and razor templates might not be the cleanest/dry-est solution but would make the implementation super straightforawd.
Yeah there is basically no real difference between MVC or RazorPages or BlazorStaticServer pick your poison depending on your preference. Personally I wish the .NET team would just add components to MVC and RazorPages then we can forget about Blazor.
Yes but in 6 months react will release a compiler to catch it up by a lot. Performance has diminishing returns and at some point, things just need to be fast enough (see vscode) and the industry will continue on as the switching cost is way too high.
True. But if the sites performed well (big if) and feel responsive, look nice, don’t break middle click and other browser functions - well I don’t see the problem, then. I don’t think the “hate” is irrational.
Which is why I think react (and other SPA frameworks) are now pointing beginners to full stack frameworks like nextjs, remix etc where those best practices are baked in. It took the JS frameworks a bit to find their path there but I think they are there now.
What are your thoughts on things like HTMX though, which with a small payload allow lots of SPA-like features and part of the content language itself. The other hatred I have is the need for all of this crap on top of a crappy language.
HTMX has a ceiling on how interactive/complex you can make your site [1]. If you know you will never need to exceed those sure. However I like to use nextjs as it gives me the peace of mind I will always be able to pivot or implement whatever the customer wants.
that's true[1] but there is also the programmer dictum "You Aren't Gonna Need It" (YAGNI)[2]
it very much depends on the type of app you are building, but I think many web applications could at least start with htmx and then, when more complex user interactions present themselves, use an island of interactivity approach that localizes the complexity.
this keeps overall system complexity as low as possible for as long as possible, and you may never need to go beyond htmx, which can lead to a much less complicated codebase [3]
I think nextjs does lead to a very simple codebase at every step of the interactivity gradient. You can have pure server side rendered HTML all the way up to full blown SPA and everything inbetween with just one tool rather than having...
1. HTMX itself
2. Your backend language Go/Java/whatever
3. Whatever JS framework for your interactivity islands
But yes we are all on the same team here of reducing complexity in the codebase and if HTMX works for you go for it.
jQuery fell apart HARD when you started to build larger/more complex apps with it. I don't think there is anyone actually nostalgic for that time that actually went through it. For a while SPAs had their own disadvantages vs MPAs but newer web standards and SPA frameworks adopting SSR have basically solved those problems nowadays.
