Hacker News new | past | comments | ask | show | jobs | submit | lawik's comments login

But animated gradient outlines on text is the only use-case I care about.

"Use case" is written without hyphen https://en.m.wikipedia.org/wiki/Use_case

Hyphenation of multi-word nouns is a process in English that usually happens after some time of usage as separate words. It often happens before eventually merger into a single compound word noun. Such as: "Electronic Mail" to "E Mail" to "e-mail" to "email".

Given how often it is used as a jargon term in software development, I can absolutely see this usage of "use-case" here as a "vote" for the next step in the process. Will we eventually see "usecase" become common? It's possible. I think it might even be a good idea. I'm debating adding my own "votes" for the hyphen moving forward.


I have to differentiate myself from LLMs by using words wrong though

I think this proving out the concept. A dev board costing. 150 doesn't matter for professional projects. It latters for tinkerers. What matters is unit price for desired qty.

And this has 4G/LTE (because it is a smartphone) so comparisons to base RPis are largely irrelevant.

And in industrial embedded Linux stuff there is essentially no correlation between price and performance. Most don't need performance and they aren't really cost-optimizing this bit of the production line very hard. It just needs to be certifiable, reliable and replacable.

I do hope they come down a lot in price and prove this out over many more phone variants.


> It just needs to be certifiable, reliable and replacable.

I think those are some good unanswered questions here. The supply of used phones is pretty cyclical, and almost all of them are out of production when their supply peaks.

Also pretty much all smartphones rely heavily on components without data sheets and with proprietary firmware blobs that won't be updated or patched without first-party support, or at all.


> And this has 4G/LTE (because it is a smartphone) so comparisons to base RPis are largely irrelevant.

Yes? So have countless new phones at around 150€. Including screen, battery, case, and warranty.

Edit: Just for fun, a list from a german shopping/comparison site, aptly named 'scrooge', selected for LTE, at least 2GB RAM, Octacore, Android 15 to not get too old stuff, in stock, 4 days delivery max, capped at 150€ incl. delivery. Sorted for lowest price first:

https://geizhals.de/?cat=umtsover&xf=10063_15.0~2607_2048~26...

Editoftheedit: To stay with the terminology of the 'largely irrelevant base RPI', they've built (or intend to?) a base board for whatever they are using as CM/Computemodule to plug into. I see some GPIO, some USB, one Ethernet.

A little bit of board layout, soldering of mostly passive components, and that's it.

Best of luck. (LOL)


A lot of the glory of Elixir and Erlang are in that you can write code that is very straightforward but performs well.

There may be cool cases for extra GenServers or gen_statems but a lot of uses of Elixir and Phoenix don't warrant making any fancy architectural choices. Partly because the runtime is already fancy for you.


No benchmarks. Hard to take this seriously.

AI voice will detract because voice is very important in video. Especially in essays. And AI voices are very common for low effort slop video so it would not be novel.

But it is not necessarily a dealbreaker. Good research, good writing, funny timing, great editing. All of these can elevate the whole. Or being exceptional at one or two can compensate for missing one.

CGP Gray does well without a face and started with terrible animation.


All names are unfortunate. There are too many things.


Seems smart to start by contributing a more openly governed path. If Matt starts to fight, sabotage and shut that down it gives the important yeah-we-did-try style cover to the reasonable next step of forking.

By being unreasonably reasonable in this way I would expect they bring the most members of the community with them if a fork has to happen.

They also leave a door open for Matt to leave this effort alone or even welcome it. A potential road to recovering trust over time.


I think it is very accurate and should be uncontroversial to say that Elixir/Erlang/OTP are very angled towards building services. I'd say service rather than server because I don't think it is necessarily about client/server as much as doing a long-running job. Which very often is a server but I've done bots, workers and whatnots that I wouldn't necessarily think of as servers.

I think the language and ecosystem are fairly general-purpose but there are definitely a lot more general ecosystems. I think some of the big wins both Erlang and Rails have achieved (that Elixir build off of) have been about constraining the problem to be "a service" or "a web app with a database".

So you are spot on there.

One of the things I've found Elixir to be surprisingly nice for is as a replacement to my Python and Bash scripting. Shelling out is occasionally awkward but Mix.install is glorious and Task.async_stream is hilarious.


I would assume it was an internal post-mortem. Far from all are public affairs.


Also I think the incident is over 10 years old as well, if it's the problem I think it is.


There is a separate implementation for really constrained device use, called AtomVM.

There are many dead efforts to implement something like the BEAM or OTP within other ecosystems. Usually not as a VM.


I have seen attempts at actor systems like erlang/beam's. Scala/Akka seems to have been a success?

Share nothing, green-thread/coroutines also seem popular now a days.


C++ Actor framework is also considerably popular, and Scylladb has their own framework which I believe does something similar.


Foundationdb also has it's own C++ actor framework.


Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: