Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
terandle
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
5 ms
·
1.
▲
by
terandle
7mo ago
Wow a human employee in walmart in 2040, very optimistic take.
2.
▲
by
terandle
10mo ago
https://artificialanalysis.ai/evaluations/omniscience
3.
▲
by
terandle
11mo ago
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.
4.
▲
by
terandle
11mo ago
It's a good idea in theory, the perf just needs to be better. Maybe with bun.
5.
▲
by
terandle
11mo ago
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 balan
6.
▲
by
terandle
11mo ago
> 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
7.
▲
by
terandle
11mo ago
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
8.
▲
by
terandle
1y ago
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 smal
9.
▲
by
terandle
1y ago
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
10.
▲
by
terandle
1y ago
Blazor is not good at anything. Please stick with JS for the frontend .NET devs. You'll thank me later.
11.
▲
by
terandle
1y ago
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 abo
12.
▲
by
terandle
1y ago
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 time
13.
▲
by
terandle
1y ago
Seems like Linus should be able to tap someone else to do 6.17 while he is on vacation
14.
▲
by
terandle
2y ago
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
15.
▲
by
terandle
2y ago
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 w
16.
▲
by
terandle
2y ago
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 t
17.
▲
by
terandle
2y ago
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
18.
▲
by
terandle
2y ago
If building a SSR site with nextjs use react server components and react context If building a SPA site with vite use tanstack/react-query and react context. There are other great libraries like zustand and jotai that can make sense in
19.
▲
by
terandle
2y ago
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
20.
▲
by
terandle
2y ago
Being able to <Context value={1}> instead of <Context.Provider value={1}> is also a nice, albeit small, QOL change. Feels like they are really honing down the API. Esp once they kill off useMemo and related hooks with the compil
21.
▲
by
terandle
2y ago
They did solve it (from the guy that originally reported the suspense issue): https://bsky.app/profile/tkdodo.eu/post/3layw6wk5bs2b
22.
▲
by
terandle
2y ago
Hacker News is a bunch of older grumpy folks that want to keep using jQuery. Also some had a bad time with classic redux patterns that were a terrible atrocity - but also not reacts fault, however they have a strong association with each ot
23.
▲
by
terandle
2y ago
Pretty easy to add runtime validation at the edges with Zod https://github.com/colinhacks/zod Great thing is that the zod schema also doubles as your typescript type so you don't have to write a duplicate/sha
24.
▲
by
terandle
2y ago
Seems to be a lot of negativity around RN, and I can understand that if you haven't used it in a while. But these days I have nothing but great things to say about React Native when used with Expo. It's great to want custom bespok
25.
▲
by
terandle
2y ago
Great release! People should be much happier with the new caching defaults.
26.
▲
by
terandle
2y ago
This is why I think react is still the best: In react you only deal with plain values. You never have to worry about wrapping a value in an observable or calling it in a function with a tracking context. Or .valueing it or whatever. It look
27.
▲
by
terandle
2y ago
Beware the footguns! https://mareks-082.medium.com/dark-side-of-the-primary-const... Let's just say they could have done a much better job on it. It feels rushed and haphazard for such a mature language.
28.
▲
by
terandle
2y ago
Been using .net since 2.0 and nah C# has jumped the shark. Primary constructors are a very poorly designed feature that for some reason was added in the last version. The new-ish yearly release cycle I think is mostly to blame, they feel li
29.
▲
by
terandle
2y ago
I would say react server components are fundamentally different. PHP starts off powered by the state on server (database etc) and ends there when it hits the client unless you hand it off to a completely different language/system: Java
30.
▲
by
terandle
2y ago
Is Singals coming to Angular not shiny object syndrome?
More ›