There are diminishing returns, especially for more mundane tasks. Fable is nice, and I bet Sol is also nice. But there really isn't much of a difference right now when using something beyond Opus or presumably Terra for most things. They're most useful when doing greenfield, highly complex/novel tasks. When Open Source catches up, it will be more widely adopted.
HN user
TheCoreh
Yeah, not only the name: they’re also going with various semiotic signs that are strongly associated with a subscription service, including their website design, choice of typography, and even the press release–style copy.
Looks like they have been acquired by Cloudflare, and pivoted to fully open source, but they haven’t really tweaked their messaging to make that fully land with unsuspecting visitors.
It’s kinda like the reverse situation of open source projects that switch to a source available license, but keep the aesthetics of an open source project. Kinda funny!
This is malware. It's doing something the user doesn't acknowledge or want, that has potentially destructive/negative consequences. Expecting users to have read the website (when they can might have installed this via a package manager, for example) is not reasonable.
The GPL imposes conditions on your use of the code / program, as does the MIT License.
No, they impose restrictions on your redistribution of the program. (And derivative works)
Which is why it's always been silly to present something like the GPL as an EULA in installers, for example.
You can introduce a social/trust element to it, something like: Join our Discord, chat to us, come to our "office hours" video calls first, then you get to contribute.
Maybe also limit the size/scope of external contributions (only small bug fixes allowed for your first few PRs)
This is not a regular code review of new code. The original code still exists, and is sitting side by side, just in a different language.
You'd be just looking at both files, side by side, to make sure nothing was lost in translation or newly introduced.
A bit sad to see this. Of course they are free to do it the way they prefer, and there are successful projects like this (Notably SQLite) but there has to be a reasonable middle ground between "everyone can just flood us with 30,000-line 'Claude implement feature X make no mistakes' PRs" and "we're not open to outside contributions"
It's not impossible, or even that hard to review the entire rewritten codebase.
10 engineers each reviewing 5,000 LoC a day for 20 days can do it.
And that is being highly conservative with the estimate. A good chunk of the the code is probably highly trivial boilerplate one can easily skim over in minutes.
To get to the point where these artificial gates substantially matter for interop, you've already cleared 99% of the hurdles, and you can get away with just spoofing the User Agent string most of the time.
Widevine is legitimately a “gate”, but realistically it only stops 4K playback on Netflix, Disney and a few other streaming sites. And it's not super relevant considering that Zen has gathered 10M users without it.
I'm honestly surprised they weren't before
This seems like a very reasonable system to ensure e.g. you and your classmate/friends can still interact as you grow up and switch age brackets. I wonder how families etc deal with it though? Can you play with your younger sibling/cousin? Is there some sort of parental approval/override?
We don’t have corporate funding
I thought you were owned by Mozilla? A corporation that has over half a billion dollars in yearly revenue? If they decided to allocate zero funding to you, wouldn't it be vastly more effective to start some sort of campaign/movement (either internal or external) to get that funding back, or to entirely fork and leave Mozilla to be your own independent project, than to ask for random donations?
Can a Roulette wheel set find vulnerabilities in software?
Yeah if I understand it correctly, this is more like 2160p@2x which is... unusual?
You don't need exclusive, 24h access, so people can pool, share or rent the hardware. Solar energy is also now cheap enough that it likely won't really be a problem.
Given how fast the Open Source models have been able to catch up their closed-source counterparts, I think at least on the model/software side this will be a non-issue. The hardware situation is a bit grimmer, especially with the recent RAM prices. Time will tell: if in 2–3 years time, we can get to a situation where a 512GB–1TB VRAM / unified memory + good fp8 rig is a few thousands and not tens of thousands of dollars, we'll probably be good.
Many microwave models have this. It's either a dedicated button or holding a specific button down
Or, at best, near-zero.
Looks good.
A minor piece of feedback, though: might be just me, not sure if anyone else has this pavlovian conditioning, but seeing the black banner/bar on top with the YC logo/color below and HN background color immediately makes me think someone passed away.
There have been many, many, desktop improvements since 1995, some of which came from the Mac, some came from Windows and some came from UNIX/Linux & friends.
- Arguably the dock, though it's probably contentious - Ubiquitous instant search (e.g. Spotlight) - Gesture-based automatic tiling of windows to left/right side of the screen, tiling presets - Smooth scrolling, either via scroll wheel or trackpad - Gesture-based multi tasking, etc - Virtual desktops/multiple workspaces - Autosave - Folder stacks, grouping of items in file lists - Tabbed windows - Full-screen mode - Separate system-wide light and dark modes - Enhanced IME input for non-latin languages - App stores, automatic updating - Automatic backup, file versioning - Compositing Window Managers (Quartz, Compiz, DWM, modern Wayland compositors...) - The "sources bar" UI pattern - Centralized notification centers - Stack view controlelr style navigation for settings (back/forward buttons) - Multi device clipboard synchronization - Other handoff features - Many accessibility features - The many iteration of Widgets - Installable web apps - Virtual printers ("print to PDF") - Autocomplete/autocorrect - PIP video playback - Tags/Labels - File proxies/"representations" - Built-in clipboard management - Wiggle the mouse to find the pointer
None of these can be said to be at their final/"perfect" form today, and there are hundreds if not thousand of papercuts and refinements that can be made.
The real issue is probably due to management misunderstanding designer's jobs, and allocating them incorrectly. The focus should be more on the interactions and behaviors than necessarily on the visuals.
Just to clarify the meaning of the measurement, it doesn't mean they're 98% interoperable across everything, it's across the specific set of goals for 2025. (Which is still really good!)
I think they realized that shipping the features out of sync meant nobody could use them until all browsers adopted them, which took years, so now they coordinate
Games are super large nowadays. IIRC Steam uses P2P for the update downloads, so you should be able to saturate whatever link you have, and the SSD should be substantially faster than 1Gbps. So anyone that has a > 1Gbps internet connection should benefit from something higher than Gigabit.
Very weird USB-C port placement choices...
- 2 USB3-A on the front
- 2 USB2-A on the back
- 1 USB-C on the back
If you want to plug an external USB hard drive or SSD at full speed, you'll need to plug it at the front? Or use up the only USB-C port...
I suspect most joysticks sold today come with a USB-C to USB-C cable, so if you want to charge your controller you either need to plug on the back, use an adapter, or get a USB-A to USB-C cable?
Also the single USB-C port isn't Thunderbolt/USB4, and they're only including gigabit ethernet, which is disappointing but perhaps understandable if they're trying to keep it at a low price.
These remind me of the Elliptic Curve pieces from another post on the HN front page right now (https://news.ycombinator.com/item?id=44315321) I wonder if the poster was inspired by that one to also post these here?
Anyway, these are pretty cool/unique looking! I hadn't seen curved origami like this before.
The jobs created by the need to build and maintain robots (and industrial machinery in general) are very few compared to the amount of jobs the machines replaced. The new jobs that the industrial and other technological revolutions created were mostly in other economical sectors, like services and commerce.
This is perhaps why it took us this long to get to LLMs, the underlying math and ideas were (mostly) there, and even if the Transformer as an architecture wasn't ready yet, it wouldn't surprise me if throwing sufficient data/compute at a worse architecture wouldn't also produce comparable emergent behavior
There needed to be someone willing to try going big at an organization with sufficient idle compute/data just sitting there, not a surprise it first happened at Google.
Is the LLM essentially playing "Wordle" with an external system that rates the quality of its output, gradually climbing the score ladder until it produces good results?
It's in the documentation for Spotlight:
https://support.apple.com/en-gb/guide/mac-help/mchlp1008/mac
I agree that discoverability could be better, but macOS has pretty consistently had hidden power user shortcuts and modifiers, to keep the basic workflow streamlined/simple for those who don't need it.
like Microsoft with its TypeScript rewrite in Go
My understanding is that Microsoft chose Go precisely to avoid having to do a full rewrite. Of all the “modern” native/AoT compiled languages (Rust, Swift, Go, Zig) Go has the most straightforward 1:1 mapping in semantics with the original TypeScript/JavaScript, so that a tool-assisted translation of the whole codebase is feasible with bug-for-bug compatibility, and minimal support/utility code.
It would be of course _possible_ to port/translate it to any language (Including Rust) but you would essentially end up implementing a small JavaScript runtime and GC, with none or very little of the safety guarantees provided by Rust. (Rust's ownership model generally favors drastically different architectures.)
If your hobby project consumes libraries which are not already locally available on your machine, this same restriction would also apply when using gcc/make/vim. (e.g. say you want to use zlib, you'll need the zlib-devel package)
If the packages are already available locally, cargo works offline.