skysight-inc/HackerNews huggingface dataset:
How do architectural bottlenecks due to modified Von Neumann architectures' debuggable instruction pipelines limit computational performance when scaling to larger amounts of off-chip RAM?

Tomasulo's algorithm also centralizes on a common data bus (the CPU-RAM data bus) which is a bottleneck that must scale with the amount of RAM.

Can in-RAM computation solve for error correction without redundant computation and consensus algorithms?

Can on-chip SRAM be built at lower cost?

Von Neumann architecture: https://en.wikipedia.org/wiki/Von_Neumann_architecture#Von_N... :

> The term "von Neumann architecture" has evolved to refer to any stored-program computer in which an instruction fetch and a data operation cannot occur at the same time (since they share a common bus). This is referred to as the von Neumann bottleneck, which often limits the performance of the corresponding system. [4]

> The von Neumann architecture is simpler than the Harvard architecture (which has one dedicated set of address and data buses for reading and writing to memory and another set of address and data buses to fetch instructions).

Modified Harvard architecture > Comparisons: https://en.wikipedia.org/wiki/Modified_Harvard_architecture

C-RAM: Computational RAM > DRAM-based PIM Taxonomy, See also:
https://en.wikipedia.org/wiki/Computational_RAM

SRAM: Static random-access memory
https://en.wikipedia.org/wiki/Static_random-access_memory :

> Typically, SRAM is used for the cache and internal registers of a CPU while DRAM is used for a computer's main memory.
Clojure hosted on Go is something that I really hope gets more attention. Clojure being built on top of Java is a fine decision, but I would love to use clojure to compose the ever growing library of stable packages that exist in the Go ecosystem.

other related packages:
https://joker-lang.org/
https://github.com/nooga/let-go
For the general population. For those who work on poultry farms they're going to continue recommending regular boosters. Chicken droppings can be a source of the bacteria.
Typical, they release this on the day I pick up a brand new A770 16gb to toy with LLM stuff.

ah well. pretty sure it'll do for my needs.
Ugh, this bug and the "Queston" typo completely broke the immersion. I can't fight my warp core properly in these conditions.

Edit: I think the "charge" is earned when the enemy move is completed, but the logic is buggy. Pretty fun first game nevertheless.
The Journey of HyperPhysics [video]
here's an example of a fairly interactive site that switched to htmx with significant savings:

https://htmx.org/essays/a-real-world-react-to-htmx-port/

htmx triggers and responds to events, which can be used to integrate it into more interactive experiences, e.g.

https://htmx.org/examples/sortable/
Yep, this thread has a good compilation of ROCm woes: https://news.ycombinator.com/item?id=34832660

That said, for hobbyist inference on large pretrained models, I think there is an interesting set of possibilities here: maybe a number of operations aren't optimized, and it takes 10x as long to load the model into memory... but all that might not matter if AMD were to be the first to market for 128GB+ VRAM cards that are the only things that can run next-generation open-weight models in a desktop environment, particularly those generating video and images. The hobbyists don't need to optimize all the linear algebra operations that researchers need to be able to experiment with when training; they just need to implement the ones used by the open-weight models.

But of course this is all just wishful thinking, because as others have pointed out, any developments in this direction would require a level of foresight that AMD simply hasn't historically shown.
Neat, the macros even work:

(->> "you"
strings.ToUpper
(fmt.Sprintf "hi %s"))

(doto "hi"
fmt.Println
fmt.Println
fmt.Println)
There was never any proposal for any system that bans people from paying for their own care :|

You’ve been duped.
That's amazing! My son is also 9 and while I haven't even attempted to teach him coding, he would probably enjoy playing this game more than writing one! My only comment is to join in with the rest of the comments here and say how wonderful it is to see this (genuinely fun!) game and to encourage him to do more!
We've built many production apps using LiveView. It has some limitations inherent to its design, namely the need to have a semi-reliable WebSocket connection to be able to effectively use the app, but with this tradeoff come a number of advantages:

- code generation makes for an extremely productive experience that makes standing up an actually-useful application very fast
- Elixir is a great language, especially for the web, and using it to render the frontend feels like having the full power of the language plus the simplicity of HTML (with little/no writing JavaScript)
- it's extremely efficient since only tiny changes are sent over the WebSocket when data is updated on the server
- you're already using WebSockets, so adding any kind of real-time functionality is very easy (chat, notifications, game state)

Because of the separation of concerns by convention (i.e. keeping business logic in Contexts), it's also a very viable pathway to build a webapp using LiveView first, and serve an API once you need other types of clients (native apps, API consumers) with minimal changes. Ecto is also great to use for validations, and having that available for "frontend" code is a pleasure. It's also great to be able to have backend and frontend tests in Elixir.

We've hit some bugs and gotchas over the years leading up to this 1.0 release, but it has long felt like a stable, well-built library that keeps our codebases simple and maintainable, which lets you move fast.

Congratulations to Chris, Jose, and all the other wonderful contributors!
Adaptive driving / glare-free lighting is legal in the US and Canada now and is supposed to reduce that problem
The problem isn't the disagreement in specifications. It's the poor German quality control that doesn't prevent these mistakes from happening. This wasn't a significant problem when the parts were physically different for different markets and the assembly line would ensure the wrong parts weren't present.
I think the title is misleading. This isn't really about either language in production environments. As other commenters mentioned, a post about production would cover topics like whether there were any tooling / dependency updates that broke a build, whether they encountered any noticeable bugs in production caused by libraries / run time, and how efficiently the run times handle high load (e.g., with GC).

This is more about syntax differences. Even then, I'd be curious how well both languages accommodate themselves to teams and long term projects. In both cases, you will have multiple people working on parts of the code base. Are people able to read and modify code they haven't written -- for example, when fixing bugs? When incorporating new sub components, how well did the type systems prevent errors due to refactoring? It would be interesting to know if Haskell prevents a number of practical problems that occurred with OCaml or if, in practice, there was no difference for the types of bugs they encountered.

This blog post feels more like someone is comparing basic language features found in reviews for new users rather than sharing deep experience and gotchas that only come from long-term use.
You’re using performance on consumer HW to conclude about abilities to build data center stuff?

You realize they already have their own ARM CPUs and run their own NVME drives with their own controllers right? And these generally outperform others in the same class.

And all this ignoring that kindle and Alexa are both market-defining products that either dominated (kindle) or created a new market that didn’t really exist before (Alexa).

There’s valid criticisms to levy, but try to be dispassionate and analytical as emotional comments don’t raise the bar for discussion. For example, I don’t really see how Alexa is really all that different from the design of any other smart speaker. They all appear to be fungible with different ecosystems accessible to them. Not sure about TV and phone products, but I’m not aware of any competitive ebook readers that offer a competitive mix of ease of use, price, etc (haven’t looked in a long time so my perception here may be dated).

And it’s important to note that they’re focus on training acceleration with these chips which is the path Google took with their chips. No reason to believe that they won’t be successful here for similar reasons in that a purpose built accelerator can outperform a general purpose design like a GPU.
Maybe this helps make your point [0]. The data purchased and
aggregated so seamlessly now that standardised 'one-click' software
similar to X-keyscore (Locate X) is widely available for tracking
citizens.

[0] https://www.404media.co/email/f459caa7-1a58-4f31-a9ba-3cb53a...
Regarding people who were mean to Big Don, no matter what industry or whether they in fact have a right to be mean to Big Don *
Zipcar outage: Complete app dependency
> Sucks to really only have one valid option on Linux atm.

I don't think that's a super fair shake? Intel iGPUs have been around for a while if you had a laptop chip or iGPU-enabled desktop chip. They've supported Linux just fine for ages, and will fill any non-3D application you might have.

And Nvidia chips are quite good on Linux nowadays - Wayland has been very usable since the 535-series drivers and nearly flawless since 550. You're right to be apprehensive about proprietary GPU hardware but I think there are plenty of options on the table right now.
If you were only one person (big if), you would also experience things and drift. Would you stop being you at that point?
Phoenix creator here – excited to finally have shipped this! Happy to answer any elixir/phoenix/liveview questions.

In case folks missed it, buried in the blog post is a new installer that lets folks try out elixir/phoenix in seconds. It installs elixir and generates a new phoenix project from a single command:

osx/linux:

$ curl https://new.phoenixframework.org/yourappname | sh

windows powershell:

> curl.exe -fsSO https://new.phoenixframework.org/app.bat; .\app.bat

You can visit those url's directly to see what the scripts do. It extends the official elixir prebuilt installers: https://elixir-lang.org/install.sh and
https://elixir-lang.org/install.bat

edit: You can see it in action here:
https://x.com/chris_mccord/status/1864067247255306332

Of course we also have non |sh installation guides if that's what you're after:
https://hexdocs.pm/phoenix/installation.html

Now that this is out, I'm looking forward to put together a few new demos. What would folks like to see? Happy hacking!
I found it very satisfying when the opponent got a question wrong. Math is hard, even when you’re an awesome monster like a flying snake or black hole.

I didn’t understand the “charging” mechanic. A little more explanation or some visual that shows charging would help.

Pretty sweet game! Keep it up!
Rust’s release cadence is 6 weeks not 6 months.
> I have been warning you for the best part of a year that generative AI has no killer apps and had no way of justifying its valuations

I like that a counterpoint to that assertion is trending on HN currently right next to this article: https://news.ycombinator.com/item?id=42312121
US officials urge Americans to use encrypted apps amid unprecedented cyberattack
I'm not sure how much of this I believe, but it's at least a useful counterweight to the irrational enthusiasm around GenAI.

In particular the "scaling laws" stuff is not paying attention to the fundamentals of where the scaling is coming from, and what the bottlenecks will be.

The consistent gains in batteries and solar and wind are a much more bankable prediction, IMHO.
re: (1) I know what you mean, but the prompt component is a great way leverage browser UI for input without affecting the rendered website, so it makes good sense in this case.
People may bring ego into programming because of some kind of pathology (eg the need to always be right or in control) but I think in many cases it's because they truly care about the work. And the problem is not that they truly care, but that there is a mismatch between the amount of influence/control/autonomy they wish to exert on their work and the amount they are actually able to exert on it.

I wasn't there, but my understanding is that essentially all programming in 1971 was done in large corporate settings or universities/research institutions. Those are environments where it's rare for any individual (even someone nominally in charge of a project) to have full creative and technical control over something, and even when they do, it only lasts as long as the project/grant or until their employer puts them on something else.

Compared to the 70s there are effectively no barriers to a passionate engineer starting their own software project as either an open source project or in their own startup, and I'd argue that those are settings where it's actually highly beneficial to bring ego into programming. It's pretty much the same notion as "founder mode" or why BDFL is one of the most popular forms of governance for FOSS.

Personally I'd recommend anybody who "brings ego" to their dayjob to take a stab at FOSS or a startup rather than trying to fit a square peg (caring a lot about their work) into a round hole (the realities of working on large projects).
Making me do math on my lunch break? This is outrageous
It can be more complex than that.

When we shipped React-Redux v8, we rewrote our internals to drop our own subscription management logic, and switched to React's new `useSyncExternalStore` hook instead. However, `uSES` only was added with React 18, and we still wanted to support earlier versions of React that had hooks (16.8+, 17). So, we defaulted to using React's "shim" package that provided a backwards-compatible implementation of `usES`, at the cost of a bit of extra bundle size.

Once React 18 reached sufficient adoption, we wanted to drop the use of the `uSES` shim package and use the built-in version, but that required React 18 as a minimum dependency. So, we did that in a major, React-Redux v9.

Code _using_ React-Redux never changed in the slightest - it's still the same `useSelector` calls either way. But given that anyone attempting to mix React-Redux v9 and React <=17 would have it break, that was clearly a major version bump for us.
A bit of a different - experimental - tool I've built for macOS. This one helps you ponder decisions among 2-3 options over several factors of different weights to arrive at a logical conclusion. I'm in the process of building 26 open-source macOS apps, one for each letter of the alphabet.
Can’t vouch for the veracity of this[1] but, if true, it’s a pretty damning indictment on the Cyber Truck’s popularity.

Just watched one YouTube video where the hosts daughter was bemoaning that they were no longer the only Cyber Truck in the neighborhood and that there were now two more owners and how much this lessened her happiness in the thing.

That’s what happens when people buy into an ideal that’s in reality just an expensive toy.

[1] https://teslamotorsclub.com/tmc/threads/only-2-5-of-cybertru...
> with no appeals process

Wouldn't it have to hit a traffic court at some point?
Here: https://archive.is/316Ps
I get "panic:" at the REPL once it loads. :(

The implementation of the [HAMT][1]-based vector in Go is [interesting][2].

[1]: https://infoscience.epfl.ch/server/api/core/bitstreams/f66a3...

[2]: https://github.com/glojurelang/glojure/blob/main/internal/pe...
Proxmox is generally run in a client-server arrangement where Proxmox and its VMs are on a server somewhere and users connect from a lightweight (probably browser) client. So the idea is that the device you use directly is a Chromebook acting as essentially a thin client, and then your real work happens in VMs on proxmox. Notably, those VMs can include Windows while containing it and not having to deal with Windows on hardware. (And I mean yes you could have a Chromebook thin client connecting to a server running a different instance of ChromeOS... and I can see ways for that to be useful, even... but that's not the idea being espoused here.)
Well, we've had a bit of a set back on the Jetpack client. Unfortunately the Jetpack developer just moved on to another position. The client is nearly ready but kind of a kick in the pants to have to find someone new right now.
Why did you upgrade?
> Imagine your favorite activity that you can do for free even on weekends. Look for such a job.

Sounds like a good way to start hating your favourite activity.
There might be an hen-egg problem if the apps end up requiring a 128Gb AI accelerator card. You only get the card if there are apps to run, and you only develop the apps if the cards are wide-spread. With so much RAM, the cards will not be let's-through-them-into-a-cheap-build cheap.

I think there have to be a couple of killer apps that run "OK" with CPU or GPU, but would run tremendously better with such a card.
Congratulations to Chris McCord and anyone who worked on Live View, what a ride since the first public version in 2019.

Although I sadly stopped using Elixir/Phoenix/LV for new projects I still have some in production that I was waiting for the 1.0 release to update.
Shout out to TRASH stack:

Tailwind
Rust
Axum/Askama
SQL storage
HTML frontend
I've noticed that some of the worst ego-related issues arise from people who care the most about their work -- the craftspeople, if you will. There is a type of person who will pour their entire soul into creating the most ideal expression of whatever it is they are trying to do. Sometimes that level of investment is warranted and even required. But mixed together with others who don't -- or can't -- operate that way, that's what leads to trouble.

I've seen this manifest as long and scathing code reviews, attitudes of "give me that; I'll do it myself," low morale, burnout... I've never found an adequate solution. Sometimes it was my ego that was the catalyst in a situation. I recognize it now, could I have caught it earlier?
Claude is familiar with all of them, and can describe each in terms of others without risking company code :-)
Background tune needed!
It seems to be that it is faster and cheaper with slightly lower than SOTA quality. There’s an emerging subset of AI companies building features on “good enough” lightweight models: https://www.wired.com/story/how-do-you-get-to-artificial-gen...

So I guess that’s who it’s for.

I’ve only spent an hour with it though obviously.
A read that book a couple years ago and thought it wasn’t very good, probably the worst of the “classic” 20th century texts. The Psychology of engineering is underrated though and someone should really write a new book on it.
I love Phoenix
Just bought a "smart" TV from Costco after careful research to insure that it could be configured to use as a "dumb" display.

I will add my own "smarts" that I can control, thank you very much. The TV is not connected to the internet and has no way to ascertain the source of the info being displayed on it.

It's sad and kinda disgusting that you have to go to such lengths just to watch TV and video in private.
No

Broadly Parliament is split into 3 camps, the left, the centr, and the right, all pretty much even. Any two could work together as a coalition and agree to a leader, but that is proving harder.
Inertia is stored energy. To emulate an energy storage, you need to be able to get energy from "somewhere". That's just physics. Plus, it works both ways: If there is excess power, you also need to dissipate power from the grid.

But an individual solar inverter fluctuates wildly, and has no significant amount of energy stored (e.g. in capacitors). It also has no place to put power (okay, you can put it in the PV panels to produce heat, but they won't like that during a hot summer day).

That's why they are using batteries to emulate inertia: They are energy storage, and thus can act like inertia. Both putting energy into the system and "removing" it. The power industry is slow moving, so we're only seeing it now.

(Not an EE, but I think the reasoning is sound. Proper EEs feel free to teach me)
You live in different worlds.

Pretty much everyone who depends on small business in NYC hates the government and law enforcement of NYC and sees them as revenuers (Louis Rossman covers this in detail on his youtube channel, to mention someone who's respected here on HN). The idea that someone would help them for a cut is incredibly disgusting to most people who live in this world.

It's incredibly foreseeable that some guy in the cab of a box truck who's distracted with his dispatch iPad looks up to see some guy taking pictures, puts two and two together and puts the truck in drive. They don't hire middle class techies to drive these trucks. Your morals don't translate to onto some 20yo guy from Newark. And they also don't translate into his hotheaded 16yo helper who runs with a less than law abiding crowd and you didn't see come out of the building just behind.

Like I said, the risk ain't worth my life.
I take a similar approach where I have branches named `my_feature/x` where I start with `my_feature/1`, do some stuff and make a messy commit history, then when I feel like I want to clean up the commit history I branch of that to `my_feature/2` where I rebase/squash/reorder/rewrite away and continue from there. That way if I lose something important I just go back to an earlier branch. for complex features I can easily get to 15 of these branches. And I just delete them when I'm done.

I find this works really nicely, I can periodically clean up my commit history and do a full review of my changes so far and make sure they're all coherent before continuing. And doing this regularly makes it much easier to keep the commits nicely self contained. It's like `final_version_final_ii_for_real_final.xlsx` on top of git
> Am I really going to call and complain about $1.27 a few times a year?

If they're triple billing you, they're triple billing someone else. That's worth an attorney's time.
Has anyone tried gpu passthrough to a ChromeOS flex vm
> (Hollywood/any cop tv show would have you believing the opposite)

Hollywood and cop TV would have you believe that "zoom, enhance" is a legitimate means of surveillance. I suspect most educated Americans avoid framing their understanding of surveillance around CSI and SVU.
Agree with you. Every successful team I've been on looked like this. Basically everyone just wanted to ship a thing. If that's the baseline norm, anyone motivated by politics or pecking order bullshit glow hot and everyone can see them.

I've seen multiple people fired on completely different teams for trying to walk over people in environments like this. It's amazing what those firings do to everyone else's morale. It skyrockets.

The message becomes clear "balance compassion for self and others and lets ship the thing, or you can leave."

If that messaging threatens someone, they've got work to do.
The iGPU in my 13900K cannot run my 5K display with decent performance (in a desktop environment). I chalked it up to hardware issues but it could be drivers. I am on Debian Linux.
They could redesign it to be globally compliant. As it stands now, its too big and heavy and can't be sold outside North America, even though it has supporters in other countries.
Does one illegal or bad thing make another illegal thing okay? Why bother having any sort of laws or enforcement?
Correct. It is insane. Bonkers. Absurd. How the hell can you live with that-stupid.
> elected official would likely suffice

For adjudicating traffic tolls? Why do you think election is going to produce a good outcome? Some jurisdictions would collect zero revenue while others would refuse any appeal on principle.