skysight-inc/HackerNews huggingface dataset:
Zoning is a problem, but it's not the only problem there. I think there are at least two more good ones we could discuss:

1. We actually do not have a market mechanic that exists in the United States that allows people to choose properly dense homes or neighborhoods because of a number of reasons. Search tools and things like that focus on metrics like square footage or number of bathrooms, and so people select for that "bigger is better" "more is better".

2. State departments of highways (they don't do anything besides that in most states) consist of individuals and contractor companies who have become adept and normal with building highways, and so all of the organizational inertia is on building anything that looks like a highway for the safety of drivers, to the detriment of everyone else. Since only highways get funded and built in most of the country, we end up having other companies like fast-food restaurants build in ways that cater to the driving demographic.
Patrick McKenzie on Navigating Complex Systems (audio)
Another approach may be https://google.github.io/typograms/

Anyway, I think that mermaid.js have an advantage there in a lot of environments as it is supported by a lot of markdown renderers, I would like that ChatGPT one does that too.
Why is it insane? I'm thinking of hiring an intern to build a forum for my saas using my platform. I can have fantastic integration and make it open source to educate on my platform.
The only alternative to RO/Distillation in purity I can think of is collecting rainwater. Im still going to use RO. For the volumes of water I use and without a rainwater collection system that doesn't use plastic pipes it's the best I can do.

While it may introduce nanoplastic it also removes it from the source water so depending on the numbers it may still be better
Nope. I am an old fart living in Canada now and many memories are very rusted ;)
For gaming, AMD GPUs are generally better bang for buck than Nvidia - notably, they tend to be about the same bang for less buck, at least on the high end and some of the middle tier. The notable exception is ray tracing but that's still pretty niche.

If AMD gets their act together and get the AI tooling for their GPUs to be as accessible as Nvidia's they have a good chance to become the winners there as you can get more VRAM bang for, again, less buck.

In a market where they have similar performance and everything minus ray tracing for somewhere between 50% and 70% of the competitor's prices it will be pretty easy to choose AMD GPUs.

They already have the best CPUs for gaming and really are positioning themselves to have the best GPUs overall as well.
I'll never understand the "hooks are bad" people. I don't find useEffect confusing, creating custom hooks is a breeze, life is so much better than old class components.

When I read complaints about hooks I'm either missing something fundamental about why they're bad, or the people complaining are missing it.
There's a growing cottage industry of companies that will take older classic cars and convert them into electric cars. Obviously they don't have the range or safety of a modern electric vehicle but you can essentially customise it to your liking in every way.

Depending on whether the classic car needs any restoration it will be about as expensive as a mid to upper range electric car but as it's a classic car and most of the installs are reversible you don't have the same worries about a modern electric car being disposable junk to be discarded in 10 years, you can probably just get a new battery pack put in after 10 years or whenever and continue driving.
you can rebase between silverblue and that without full reinstalls iirc.
Older Android devices had terrible storage performance. Any time a background process is using storage, the device gets very slow.
I believe it's attributable to "wider" vs "taller" software development. As in, software using more cores, running more background processes, intermittently accessing I/O more frequently, vs software that does a single task more intensively like a game.

Games can be parallelized, but in a relatively tight way: the game just has to coordinate the physics/AI stuff with the rendering stuff. The rendering is defined in a way that lets it consume most of the resources. Games on old CPUs do hit thresholds where they stop being playable, but they are fairly concrete boundaries where that number of cores and clocks just won't hit the pacing needed for that level of detail.

But the general operating system layer has made a point of pushing both power and responsibility onto userspace applications, and allows them to be helpful and do things in the background. The applications in turn are doing a lot of redundant, overlapping work - no unified methods of serializing and communicating, polling for events, contra-user telemetry and the like - so the end result is a pileup of background load that can kill the experience.

The switch to the SSD era cured one aspect of this - background storage accesses - but just brought on different bottlenecks with memory, core, and network utilization.

The way it might be addressed is to give the OS relatively greater, higher-level responsibility and supersede more of what the applications are doing. The open-source/free-software space has a better chance of accomplishing this because, while it usually develops at a slower pace than a commercial company, it's more "sticky" in terms of accumulation at the base layer and fixing root causes instead of hacking around them. And people generally do report that installing Linux is a speed-up for their old device; when you run a contemporary Linux distro you get a lot of software that has been properly domesticated to the environment, and therefore doesn't turn into a burden.
Welcome to Psychedelics Microsing Graves, your one-stop destination for a unique and enlightening journey. Discover the captivating world of psychedelics and explore our diverse range of products that promise unforgettable experiences.
1. Discourse. Might be different for others but I had 0 time to manage the deployment, and upgrades took a lot of time.

2. I used https://www.linen.dev/ but I think there are others. It turn Slack conversations in a searchable static site.

3. Developer community for an open source software product.
> one the best things ever invented

Fire? The wheel? Penicillin?

Maybe it's just because I'm getting older, but I'm increasingly annoyed when people use these sorts of over-the-top hyperboles.
> The forest fires are because you don't recall them as a child. Forests need to burn, that's the natural order of things for millions and millions of years

This doesn't apply to many of the wildfires farther north in Canada, because no lives there in the first place. Historically the year-round moisture has made the trees "fire retardant". Now they can experience thunderstorms and burn for weeks and cover NYC in a blanket of smoke.
I don’t miss each program coming with its own set of printer drivers. Or only having one type of storage: a directly attached disk of one of a few specifically supported models. Or each program having to decode images in its own code. Or having to POKE specific memory addresses to put a dot on the screen. Each of those layers provide baseline functionality that lots of programs can use.

Most of the time, “bloat” is another way to say “the features I don’t use”. Yes, sometimes people push bad code to production. Other times it’s new inherently more complex code that makes computers nicer to use.
I've been enjoying the simplicity vanilla light-dom custom elements and minimalist express server for the API.

Lit-html for near zero-cost dom updates.

Been doing it for years, and struggle to understand why anyone would want to put up with the complexity of react.
HR in every country attracts people that do not have really qualifications in most cases to even work in HR.

Aside from that there is a visible gender discrimination in the sector towards men as well the education discrimination. When these two are combined, they act as gatekeepers, which makes the whole sector worse.

Less psychologist and more law and economy graduates was how it was before. For them the communication is the key aspect of their careers, so most of them have it under their thumb. No one really complained about old Personnel Departments and the info was there and they were actually knowledgeable about their job.

The education really can make difference sometime. As we can see, these two do not know how to handle situation, and are repeating the speech that most of the people probably already heard, without thinking.

Hell, I think that someone could make HR AI that would do the better job.
If interested, a related legal concept in trademarks is called passing off https://en.m.wikipedia.org/wiki/Passing_off
Hooks are a new paradigm? That’s news to me, hooking is at least as old as two decades when I first started programming. Hooks are, like most programming ideas, hard to understand at first but easier as time passes and you see more of them.
I agree. Up until Hooks, you could make your own toy React pretty easily if you wanted to - creating a basic, unoptimised version took a few hours. That made the whole system pretty understandable, especially for junior developers - obviously, you'd always pick the battle-hardened, optimised real React for anything serious.

Hooks fundamentally altered the contract about the API that React provided, and suddenly magic was popping up everywhere. Thankfully suspense never really caught on, because that was even more magical.

I do quite like the developer ergonomics of hooks, but it does make me wonder about whether there was a world in which we could have had both the ergonomics _and_ something less magical.

(Aside: that Medium article is available to members only.)
So last minute that the AMD engineers found out Microsoft went with Intel at the Xbox launch party [1]

[1] https://kotaku.com/report-xboxs-last-second-intel-switcheroo...
Technology has improved a lot in rockets just as it has in cars.

For thirty-odd years, the US bought powerful Soviet/Russian rocket engines instead of building its own. Its rocketry and metallurgy knowledge-base is only just now getting back to where it was around 1970. (That's basically a loss of 50 years of skills and manufacturing.)
Funny to see this now. A couple days ago I was on vacation in San Diego and visited the San Diego Model Railroad Museum in Balboa Park and a lot of the traffic flowing through my head about it are all points addressed in the above article:

"Almost everyone working here is quite old"

"The amount of space this takes up is incredible, I wonder how people get into this hobby, I've never lived anywhere where I'd have enough space to set up a model railway long term"

It's kind of a shame too, it was the first time I think I've ever really appreciated the large scale model train installations. When I was younger I'd see them at random historical museums and mostly just think "yeah choo-choo sure does go in a circle haha". I think the San Diego museum did a good job of conveying that it isn't really just about the trains as much as it's about modeling the landscapes and towns the trains actually go through. Viewing it from the perspective of a massive scale diorama of some region really raised my overall appreciation for the whole endeavour.
The cab, sensors, and compute are also expensive, not to mention other variable costs like staff for remote assistance, maintenance, and first/last mile
The economics and incentives of RNGs are interesting. If nothing is materially at stake ,an imperfect RNG, even a bad one, suffices provided people cannot easily tell, such as games. But if money is at stake or security, like crypto wallets or online casinos, suddenly it matters A TON.
I don't think it's just you. Plain hyperlinks coupled with modern connections and equipment feels fast and easy. You click and a page appears. With JS apps they just feel heavy and almost buggy even when it is just a page of text with links.

Maybe I'm just in adt and marketing ech too much but it's almost like I can't be too fast on clicking thing otherwise things get fucked up and lose their states.
Things should be pretty silent if we are in a dark forest. Unless the top of the food chain predators sometimes make noise waiting for naive preys that answer.
Is there any info to substantiate that?
We have been piloting louie.ai with some fairly heavy orgs that may be relevant: Cybersecurity incident responders, natural disaster management, insurance fraud, and starting more regular commercial analytics (click streams, ...)

A bit unusual compared to the above, we find operational teams need more than just SQL, but also Python and more operational DBs (Splunk, OpenSearch, graph DBs, Databricks, ...). Likewise, due to our existing community there, we invest a lot more in data viz (GPU, ..) and AI + graph workflows. These have been through direct use, like Python notebooks & interactive dashboards except where code is more opt-in where desired or for checking the AI's work, and new, embedded use for building custom apps and dashboards that embed conversational analytics.
> Where I have zero idea is why they went for NVIDIA Tegra that was originally aimed at automotive and settop boxes instead of Qualcomm, Samsung or Mediatek

I think a big part of this comes down to two things:

1. If you’re Nintendo, the Tegra X1 was the fastest mobile graphics chip available. Mali and Adreno weren’t anywhere close at the time. The alternative would’ve required shipping a Switch less powerful than the already-derided Wii U, which just was not an option.

2. Nintendo uses their own, in-house operating system that fits into under 400MB and runs on a microkernel. Naturally, you want good GPU drivers. NVIDIA’s philosophy is to basically make a binary blob with a shim for each OS. Not great, but it demonstrably shows the drivers can be ported with fairly little effort - Windows, Mac, Linux, Android, whatever. Qualcomm and MediaTek’s strategy is to make a bastard fork of the Linux kernel and, maybe, upstream some stuff later, with a particular interest in Android compatibility. I think it goes without saying, that the implementation which isn’t tied to a specific kernel, is a more desirable starting point.
> they always devolve into these blobs of non-deterministic async state with unpredictable performance

Exact same experience here. I've been banging this drum for years. When hooks came around I thought they might make it better, but alas, we are still in a downwards spiral. Building web apps is 10x more complicated today than it was ten years ago, with nothing to show for it.

I'm happy to see some known voices in the community realizing this, but also sad that this is how things work now. The rise and fall of React will have been both a product of social media / developer celebrities.
Yeah I never found them difficult and they’re making my life so much easier

Curious what specifically about them is difficult or hard to understand?
I don't think new paradigms are a bad thing, I think the problem with hooks is that they are a "clever trick" to work around the fact that the language/runtime does not have the necessary features to support the developer experience that they would ideally have.

What's sad is that the class-based component system did have those necessary features, it also had a nice distinction between components and their lifecycle and the rest of your code. Now with hooks, everything is React lifecycle code, unless you're really smart about your API boundaries, and in my experience no one makes good re-usable hooks that are nicely isolated from business logic.
Have you considered offering a bulk email service for folks who want to send newsletters? It looks like an interesting tool though it seems like you specifically ban that use case, even though it seems like it could be great for that.
Some people find the mental model to be very confusing. I've been writing hooks for years so intuitively, the behavior has sunk in. But I still admit that it's mind bending to try and understand how it actually works. The original commenter is absolutely correct that it diverges from both functional and OOP, and while that's not necessarily a bad thing, it's reasonable for people to consider it a net negative.
Presumeably (not my language) it frames "require ModuleName" as some thing that can be tested for whether it would evaluate.

Therefore a failure in evaluation is not the same as a failure of something "required" because it cannot be found.

It's a curious kind of hackity hack often seen (in various forms) to roughly spack fill some other deeper issue.
But all the lifecycle methods were magic that needed to be understood... hooks just let you co-locate related logic in one place instead of scattered across 3 or 4 lifecycle methods.
> Why iphone? We had internet on mobile phones before that point.

Certainly not in any way that mattered, and I say this as someone who spent the middle part of my career specifically on mobile.

I mean, sure, there was stuff like WAP, and some other niche phones that could (very, very clunkily) display full HTML. But the launch of the iPhone is what first brought the mobile Internet to the masses (and pretty much all smartphones after the iPhone aped the basic design), and most importantly, was the beginning of the change where websites started even giving a shit about mobile clients ("Mobile first" design and all that).
I'm not taking issue with the outcome described. I'm pointing out that targeting class diversity will not always result in racial diversity as claimed.
What's New in Go 1.22: Reflect.TypeFor
"useEffect" itself is not what is confusing. What's confusing is when you have many dozens of components with effects all loading state asynchronously. Some of them might even be executing callbacks passed as props from parent components. Oh, and then those effects sometimes re-execute when the effects of parent components complete and pass down updated props! It actually reminds me of programming VHDL.
Is your issue with the fact the language is functional, or that it's a DSL specific to Nix?
Your average road train which has restrictions on which roads it can drive on is 3 trailers. 4 trailer trains exist with far stricter limitations.

I just don’t see a 12 trailer 140m long road train with wires strung between the bits being feasible in any way on a road that has other, untrained users on it.
From my experience (picked up react when it came out) hooks are not objectively better than class components in a standard web app. In the more reactive scenarios hooks are great, and your app is already complex and in its own world of mental models.

Hooks enable complex patterns too easily and I think this causes a lot of breakdown in what would otherwise be simple applications.
That doesn’t cover life insurance. California law does. My relatives live in states with fewer legal protections for residents and I strictly urge them not to use DNA services.
Ok, but even if some politicians run on a platform of capping the age for eligibility to run for congress or the presidency, getting 2/3rds of the Senate and 2/3rds of the House to actually vote for it is near impossible, especially in today’s polarized (frequently gridlocked) political climate. But also, regardless of how popular this might be publicly, most politicians don’t run on platforms that curb their own power.

The last time we amended the constitution was 32 years ago, and that was more than 202 years after the amendment was originally proposed and approved by Congress. This amendment effectively does not allow Congress to get a pay raise until their next elected term. Unsurprisingly, when this amendment was brought to the public’s attention in the 1980’s, Congress majorly pushed back about it. But the amendment was gaining popularity publicly and it was ratified by 2/3rds of the states, so congress had no choice but to accept the amendment as valid. This may have been otherwise impossible to pass if congress hadn’t already approved the amendment over 200 years ago in 1789.

Just because Congress should be a certain way, does not in fact make it reality. Congress frequently makes unpopular decisions. And when you have some representatives that have an equal say in the vote that represents a fraction of the number a people of another representative, what the majority of people want doesn’t really matter politically in most cases.

Now you’re right about one thing, if this platform is popular enough, there still might be a possible path forward to achieve a constitutional amendment. But it’s far from a certainty and more likely a long shot at this point. It could take decades or more until the amendment is both approved and ratified, if it’s even politically possible at the moment. It’s not as simple as, if the people want it, they can vote for it; because that is just not the current reality in American politics.
Actually was building a program right now I'm looking at some of these challenges but I would make it a little more clear on the website that the games is just an example utilization of what you've built. From Reading here I thought it was exactly what it was and then confusion hit when I was looking at the website that it might be specific to gaming
One reason: Our ability to prototype, build out ideas, and in general innovate is more complicated and less scalable.

The fastest international delivery isn’t comparable to driving 30 minutes to shop for the parts needed for some wild idea (etc.), but that market no longer exists in the US.

In addition to delays, that makes R&D more specialized and therefore more expensive; not to mention the local loss of expertise by the sellers of the components.

Just trying to build some Arduino ideas: I’m looking at $$, planning, and days of shipping. No opportunity to try something out on the spur of the moment.
The US is number 3 in the world in both total tonne-kilometers and tonne-kilometers per capita shipped by rail, and it’s in the top 10 in percentage of freight moved by rail.

https://en.wikipedia.org/wiki/List_of_countries_by_rail_usag...
Create React App is in a strange, pseudo-death state.

- It is not listed as an option for starting a new project in the React docs[0].

- The last release was April 12, 2022.

- The last time I created a new project with CRA, it printed a console log that claimed CRA was deprecated. However, the message seemed to originate from a dependency rather than CRA itself.

All this was enough to convince me to move to Next.js for future projects; though I find Next.js overcomplicated and full of things I will never use.

0 - https://react.dev/learn/start-a-new-react-project
> The final 31 percent of the very-rich advantage comes from colleges judging these children to be stronger in nonacademic categories. That makes sense since they have greater access to extracurricular activities and leadership opportunities

This is very true imo. In my country medical school admissions are extremely competitive, and takes into account many of these factors, since there are many more ace students than slots. The results definitely favor wealthy students though, they're the ones with extra time for activities, or parents to fund groups for them to lead. Personally I think being a part-time burger flipper is better for your character than spending all your free time volunteering at a shelter to cynically maximize your resume.
One of the best things ever invented in component based frontend frameworks. It makes purely functional frameworks like modern react much easier to deal with.

Off course it's a violation of some theoretical principals. So what?

What I don't get: people complain about not being able to handle all the useEffects, but they probably shouldn't be there in the first place. In my experience most ambiguous use effects can be easily removed. They are rarely needed for anything but library code or interaction with browser APIs.
May I ask how you did it? I went with Typst because I found Markdown to be too unstructured/limiting and didn't want to use LaTeX (hard to use data from external files: CSV, YAML, JSON, etc.) templates to compensate.