I generally use conversations on this topic as a litmus test for a group or community. I’m pretty disappointed by all the whatabout-ism and false equivalence.
I expected better from HN.
We can study why this happened later. The genocide needs to stop now.
Given you just mentioned semantic search (a term I haven’t heard in over 15 years) and the other breadcrumbs in this comment, you wouldn’t by chance be an English lecturer living in Ireland would you?
I’m in the the unique (and at times, unenviable) position of spending the last 4-5 years building out a music app (getradiant.app for the curious) and I agree with what others are saying here, it’s about exposure.
My music taste has expanded and shifted a lot in the past half decade, which also happens to coincide with the first half of my 30s, mainly because I’m exposed to new stuff constantly through my consistent testing of my app.
Your 30s is typically when people start noticing the growth of the circle representing their radius of musical interest start to slow. Mainly because it collides with having less time for choice (life gets busy, responsibilities increase) coupled with a decreased capacity for new experience.
I’ve also noticed TikTok has exposed me to a ton of new stuff.
So the TLDR; is, the time you have to discover on your own will become ever more limited. Your best bet to keep the party going is to find one or two low-effort, lean back discovery services and stick with them.
I’m going to hard disagree with this. A lot of the enjoyment I get from creation is the process of others enjoying what I’ve built.
Further more, building for others is great for building out areas you’re weak or inexperienced in. Like, I was poor on the accessibility front until I found the thing I created resonated with the visually impaired folk.
It’s tangential at best but there is a better way than all of this nonsense.
Your employer can declare and direct tax owed from your paycheck directly each month. Come end of year you can click like 3 links in a tax portal to ensure you’ve not overpaid and that’s the extent of your tax worries.
We obviously don’t have a perfect system here in Ireland (far from it) but Jesus Christ America, your tax system is absolutely insane to Europeans.
- RISC-V has miles to go, I worry that with the current pace of ARM it may never catch up.
- The assertion you can’t buy UMPCs in 2024 is patently false. GPD and a whole host of manufacturers make em.
- A non mobile optimised blog in this day and age? That was a chore to read on the go.
This immediately reminded me of the Palm Pre iTunes/iPod protocol reverse engineering debacle from the oughts.
It became a game of whackamole where by Palm would update their OS (RIP WebOS) to reintroduce support for iTunes to their devices and Apple would bend over backwards to break it again.
Did Beeper not anticipate that this was inevitably coming and put fallbacks and rotational serial numbers in place if Apple start getting blocky?
My only major gripe with it is React. Either go all the way and build something for Svelte that does this lowering the bar to the bottom on both creation and understanding of the UI layer or
Do this with Rust and target Wasm abstracting away the hard / tedious parts of working with lower level languages and creating graphical applications.
Like this + Tauri would be an absolute powerhouse but as good as it is, it’s still just another React maker.
If it’s as good as you say, set up a sponsorship goal and we’ll contribute. 11 is massively expensive to use in embedded in an application so anything that’s lightweight enough to be self hosted and can produce 11 labs like output has my dollars.
I hate Gizmodo. They really do find outrage in everything, seemingly getting off on it more than their readers.
As others have said, paying 15 bucks an hour for Turk work rather than outsourcing it to Africa is a step up but even if they continued offshoring, the cost of living in other places is significantly lower and pay, surprise surprise, is significantly less (in saying that…2 dollars is a bit exploitative but that’s the market right or wrong).
Having read through the comments and tried standard notes I can see why users might have been disappointed going from native to this web implementation.
I recently went through the process of switching to a web stack from a native iOS stack when it came time to support Android with one of my apps (https://getradiant.app/) and my biggest concern was making it feel a near as possible to the native app it was replacing and having it perform as well as possible on older Android devices. It turned out quite well and I’ve never had a user complain about the transition.
The trick to my mind was to treat web dev like mobile dev. Focus on bundle size, load speed and fluidity within the confines of a mobile environment. Constantly compare what you’re building to a native app. Probably focus on SPA over SSR/MPAs. And remember, if you apply all of the above to much less restrictive desktop browser environment with a much higher performance ceiling, the experience is going to be pretty good.
TLDR; think small, think fast and start with the most constrained environment you’re targeting, usually mobile, usually older Android. If you understand the limitations and considerations of browser engines when taking into account the above, the rest will follow and you’re going to have a good time.
I expected better from HN.
We can study why this happened later. The genocide needs to stop now.