how is enabling ever bigger and more expensive to produce forms of entertainment making modern society better? remove all that and we won't lose anything. we'll always find a way to entertain ourselves. likely, with more culturally beneficial and social forms of entertainment.
HN user
osener
If you find this interesting, also check out their UI library called Bonsai that built on top of Incremental: https://github.com/janestreet/bonsai/
Libraries like React are pretty efficient with skipping work by using Virtual Dom, but constructing this vdom still takes time. Bonsai makes the vdom incremental and it is pretty fun to work with.
I built a desktop UI library with it by targeting (now unmaintained) Revery. It is using a much older version of Bonsai however: https://github.com/ozanvos/bonsai_revery
Smart people have been falling into this trap as long as LLMs have hit production. Supposedly early internal versions of GPT-4 had "sparks of AGI" but the public version was "dumbed down for safety"
In my experience restricting programs that can be expressed is a good thing, even more so with agentic engineering. The more guardrails there are, strong typing/TDD/computer use/..., the solution space shrinks and chance of a robust solution increases. Sure maybe this burns more tokens going in circles but it feels less like a slot machine more like a robot searching for a solution for a well-defined problem.
Devs have very strong opinions about dynamically typed programming languages. But reasons such as "exploratory programming", "expressiveness", "taste" that makes them feel good to program in for humans does not matter for agents. Agents don't care that the language "limits them" and prevents them from expressing the code in a succint way because it would not type check.
Surprised to see Clojure/ClojureScript come up on socials more often all of a sudden. I used it professionally for a few years around ~2012 and like many others moved off JVM and moved into typed [functional] languages.
Is the sudden buzz due to agentic coding? Does it rip through code faster with no type checking and fewer invalid syntax errors and reserved keywords to deal with? are we in for a sexp resurgence?
Ah I just switched to using https://github.com/uxjulia/crossink-reader
Not sure what KOReader is but the fonts included in this one and the overall reading experience is solid.
This is the official announcement: https://research.ibm.com/blog/granite-4-1-ai-foundation-mode...
It is not the researchers' fault that some slop got posted here instead.
It is common amongst French, Dutch etc speakers where saying "it said x" sounds unnatural.
This announcement mentions Node.js a couple of times. Does it also support Bun as a package manager and a runtime?
Cost remains an ever present challenge. Cursor’s larger rivals are willing to subsidize aggressively. According to a person familiar with the company’s internal analysis, Cursor estimated last year that a $200-per-month Claude Code subscription could use up to $2,000 in compute, suggesting significant subsidization by Anthropic. Today, that subsidization appears to be even more aggressive, with that $200 plan able to consume about $5,000 in compute, according to a different person who has seen analyses on the company’s compute spend patterns.
This is the relevant quote from the original article.
There are fast fashion attempts at this like adding elastic material to every fabric so they can get away with having fewer sizes and cuts thus less unsold inventory and availability issues. But everything has a tradeoff. In this case the elastic material degrades MUCH faster than cotton so you have to throw away your jeans quite a bit earlier compared to a quality 100% cotton denim which can last you a decade. This is very unfortunate as most of the fabric in that piece of clothing is perfectly fine and this is pure waste.
This is some next level nitpicking. It's like criticizing XCode or Idea config of someone, instead of their product (or more popularly whether their website hijacks the back button). But at least in this case the dev config is checked in and reproducible.
Ok so it is not going closed source, they are just going to extend it as they need to drive Zed features. Totally understandable for an in-house UI framework, this is why you’d build one yourself anyway. I can imagine maintaining backwards compatibility, doing releases, writing documentation and growing a community around it is a considerable distraction from their product work.
For years I thought I had a faulty touchscreen and started relying on dictation more and more. Seeing this video saved me from going insane. They must have crunched the numbers and decided that these choices benefit more people than not. BUT HOW!
We ignore for these purposes Zed's GPUI which the Zed team has transparently, and understandably abandoned as an open source endeavour
Do you have a source for this?
I understand your perspective. However, those trades, and most work in general, differ from art. Art is vital to our society, yet the current reward system optimizes for the worst art and the worst people.
We need more art that pushes boundaries and remains controversial. Instead, we favor the type of artist who attracts the most attention through their personality, whether because of their looks or a manufactured edgy image, while producing mundane, lowest-common-denominator work. We must support contemporary artists who move us forward rather than remaining stuck in popularity contests or constant nostalgia.
Under the current system, it is almost inevitable that influencers use their status to promote gambling ads and NFTs, ruining the lives of their fans. We need to break this cycle of rewarding increasingly poor behavior while making it harder for independent artists to earn a living.
When I tried it last year, their edge compute infra was just not there yet. It could not do any meaningful server-side rendering because of code size, compute and JS standard constraints.
Has this situation changed?
I have a confession to make.
I hope ChatGPT starts writing only short sentences.
Punchy one-liners.
One thought per line.
So marketers finally realize this does not work.
And stop sending me junk emails written like this.
Listen to the sound of HN hawks erupting with joy when they realize they can blame JS, React, RSC, Rust, Cloudflare, and the cloud all for one outage.
I knew plenty of office workers managing just fine using OpenOffice 10-15 years ago.
Today people are much more reliant on real-time collaboration, polished cloud and mobile experiences. Fractionalized open source software has a harder time competing with this than file based boxed software workflows of the past.
Reminds me of the headline I saw a long time ago: “50 years later, inventor of the pixel says he’s sorry that he made it square.”
https://github.com/zed-extensions/tsgo does exactly this
Former. Otherwise I would need to have multiple database instances running, each with its own data and migrations to keep in sync. Plus I would need to re-do local env vars to hook all of this up for each worktree etc. And I often want to know how these branches play together, with GitButler I can bring these branches in and out with a single “apply to workspace” click.
Somehow the GitButler workflow works great for me and it is the first VC software that made me drop Magit after a decade of daily use.
I do not use it collaboratively. I use it to continuously ship smaller things while working on bigger pieces and I constantly move independent changes around to different “lanes” to ship frequently as parts of my work mature.
With Magit I used staging area and amended commits continuously. With GitButler I “assign” files or chunks by dragging them into lanes as I am happy with the changes, and when I have a logical unit I commit it. Having this multiple staging areas has been a great workflow improvement as well.
This is cool, except I don’t want to run multiple copies of my dev stack.
GitButler does this cool thing where you can work on multiple branches at the same time, applied to the same working directory. For example you can work on the css while an agent works on the admin panel on a separate branch. It would be cool to have this with a tool like FleetCode.
A lightweight alternative to Playwright, which starts a browser instance, is using an HTML parser and DOM implementation like linkedom.
This is much cheaper to run on a server. For example: https://github.com/ozanmakes/scrapedown
Since this is marked as a departure from HTML and has it's own syntax, I think this is a good point to improve upon JSX.
- Remove curly braces from props and children
<MyComponent name="Joe" onClick=(() => canBeInParanthesis()) />
<div>userName</div>
<div>"Text contents"</div>
- Add punning (like how { age: age } becomes { age } in JS) const age = 40;
<MyComponent age />/
<MyComponent active=true /> // explicit boolean attributesPython does an exceptionally bad job. After dragging the community through a 15-year transition to Python 3 in order to "fix" Unicode, we ended up with support that's worse than in languages that simply treat strings as raw bytes.
Some other fun examples: https://gist.github.com/ozanmakes/0624e805a13d2cebedfc81ea84...
I tried Zen for a few months. I like the UX, even more than Arc in many places. But it is just too slow for me on an M1 Max. I've switched back to Orion. Even though I miss some goodies such as Firefox containers, I just need the browser to get out of the way, not use too much power and not warm up my laptop with runaway processes. Plus, tree-style tabs are great.
Ah the joys of enterprise.
Once, a team at my old job wanted to try A/B testing for the first time. After some research, they picked a SaaS tool to make it quick. Simple, right? Just sign up and go.
Of course not. First they had to go through THE PROCUREMENT! (dun dun dun dun)
Those legends weren’t about to let us limp along on a humble pro plan. They wheeled, dealed, and months later emerged triumphant: a glorious three-year enterprise contract. SLAs! Volume discounts! The whole nine yards. The art of the deal baby!
Small snag: by the time the ink dried, the original team had moved on. New PM, new priorities. No one even generated an API key during the whole time we paid for this top-tier enterprise service.