HN user
It's hard to get that point because you're conflating two different stories.
Folks around here are generally uneasy about tracking in general too, but remove big brother monitoring from Safe Browsing and this story could still be the same: whole domain blacklisted by Google, only due to manual reporting instead.
"Oh, but a human reviewer would've known `*.statichost.eu` isn't managed by us"—not in a lot of cases, not really.
How are you measuring this? I'm surprised the Web Audio API scheduling system has that much insight into the hardware latency.
Even still, both repos had READMEs [1][2] clearly meant to be read by the public. The archival was only successful years ago, with a failed snapshot as far back as 2021 [3]. This really seems like they forgot it was ever public.
Now, this is only about it being a GitHub breach. Whether unlicensed (emenel/portfolio) or GPL (emenel/dust) code should be allowed in such datasets is a different matter.
[1] https://archive.softwareheritage.org/browse/origin/directory...
[2] https://archive.softwareheritage.org/browse/origin/directory...
[3] https://archive.softwareheritage.org/browse/origin/visits/?o...
I believe the title refers to the linked article [1]—which claims it topped the platform's charts—rather than the quoted tweet.
It might not be to your liking, but it's been in Netflix's top 10 lists [2] quite a few times.
[1] https://www.independent.co.uk/arts-entertainment/tv/news/sha...
Not to knock on Sunvox or NightRadio (both awesome!), but that effect only exists in the video. It doesn't happen when playing the demo song on the software, and they confirmed it was made with a video editor [1].
[1] Highlighted comment: https://www.youtube.com/watch?v=AHFSrxlouh8&lc=UgxI33WIYq61V...
How does one move with the mouse? I could only find gestures for rotation and zoom; for movement I had to resort to manually entering coordinates in the settings.
You can use `untrack` [1] when you don't want to react to some state inside an effect.
You can still use `onMount`. It's not deprecated [2], although `$effect` could be used similarly going forward.
[1] https://svelte-5-preview.vercel.app/docs/functions#untrack
[2] https://svelte-5-preview.vercel.app/docs/runes#$effect-what-...
This only happens in "proper" tables. When you add a formula to a table column, Excel will automatically convert it into a "calculated column," so overridden values will have a green mark denoting an "inconsistent formula."
It's still a pretty minor warning and it only requires two clicks to ignore.
From the submission (the repo's readme):
We got a takedown request by openai's legal team...
Did Github take a separate action somewhere?
It shouldn't matter if it's a fast desktop or slow mobile (unless it's not keeping up, which is unlikely in these examples); what matters is the display rate on these devices. The demos feel very fast in a 250Hz monitor when compared to a 60Hz one.
A feature that deserves its own bullet imo: Wifi sync. I suppose it's akin to Keepass+Syncthing but integrated into all clients.
I used Google Drive/OneDrive in the past but a few times vaults would get into a broken state where they couldn't connect to the provider anymore and I had to manually re-connect. It was always able to smoothly recover and sync, but I had no confidence I was synced at any given moment.
I jumped on Wifi Sync as soon as they launched it and haven't looked back—as long as I'm on the same network once in a while, everything is in sync.
Sometimes I get an itch to try the open-source/Keepass route again, especially since it seems to be much improved, but Enpass is convenient for now.
The right operator for unit conversions is "in." "to" is used for ranges, so it's doing 100 euros _goes to_ 1 us dollar and giving you back the answer in dollars.
But it seems the parser is breaking when trying to do the inverse, anyway: "100 usd in eur" seems to do "e*ur" and gives "Values must be converted to units."
Did you consider Deno as misleading?
The fact it states it's powered by JSC before even mentioning Zig makes it pretty clear, imo.
I don't think 1.0 releases deserve the same treatment as 1.3.2 Beta 1.
The SNI here is that Tauri has hit stable, an information that does change how a lot of people would approach it.
I might need an even longer explanation, though, because I don't get it still. There are projects like Blender which were allowed to the front page like 5+ times in the past year, exclusively with posts about new releases. The discussions always hit the same notes. Why is that any different?
Apart from the architectural similarity, Elm also predates both Redux and Flux, even being referenced in Redux's Prior Art page [1].
[1] https://redux.js.org/understanding/history-and-design/prior-...
It still targets Erlang—but the compiler's written in Rust (from the first v0.1 release in 2019).
Could you share an example? I thought async functions weren't callable outside an `async` invocation from the `Inline` calling convention.
That seems to be the same kind of confusion I ran into the last time I tried to do async in Zig. I also had trouble figuring out who was responsible for keeping track of async frames.
The details are not fresh, but it went something like: if a function called an async function like so `the_frame = async foo();`, you couldn't really reliably `resume the_frame;` unless you were responsible for all suspend points hit inside `foo`. If `foo` tried to call some other function `bar` you had no idea had a suspend point, you couldn't resume the frame anymore since you'd need to resume the inner frame instead.
So, yeah, they were colorless as in you could call any function you wanted and they don't advertise suspend points or async usage, but they are actually colorful inside and calling the wrong color breaks things.
It's the customer's fault they didn't know Vimeo is losing money? A pretty big reason for that could be that they've been with Vimeo for over a decade in some cases and have always been led to believe they were paying for the service they were getting.
I'm confident customers' reactions would be very different had Vimeo told them "hey, you're actually costing us money, please upgrade to this plan that'll cost you about 30% more." In fact, Vimeo could have done that at 2x, 3x, 4x... But nope, let's pretend they're paying customers and reveal we've actually been subsidizing the service the whole time, but we need 17.5x the money now. And the customer is the arrogant one?
Does anyone have an opinion on Enpass' trustworthiness? It's pretty sleek, and with wifi sync I don't even need a server/cloud provider... But being a commercial application I'm not sure how to weigh its security. It also seems the last public audit is from 2018.
That's okay, but when I go out of my way to actively set the language in a service's settings, shouldn't that be honored over an assumed local-by-default? Because that's what I do with Google (individually on Search and YouTube), and it somehow forgets it quite frequently.
I was actually careful not to equate "active" with "directly reaching out to people," but taking any active means of furthering the spread of the idea.
And, yes, I'd personally consider word-of-mouth to be largely push-based. But I concede it could just as well be people asking (perhaps too many) questions.
It probably doesn't, but I think "to propagate" is easily deemed an active engagement as opposed to a passive one. eg. while one can propagate an idea by doing nothing but waiting for people to come to them, I'd expect most people to assume "let's propagate this new idea" to mean a more active role in disseminating it — even if not quite directly reaching out to people.
Interesting, that's very close. :)
Since I had a bunch of software open and the system had been online forever, I restarted and tested again — turns out it squeezed a couple of ms to ~16ms on shared-mode.
By the way, I believe the low latency stack is enabled system-wide, so Reaper should already be using it.
For what it's worth, on my game I've been piping a SunVox instance to a 128-samples shared-mode WASAPI stream and haven't encountered distorted audio, yet.
At the end of the day, I guess I would indeed default to recommending WASAPI unless one has hardware with great ASIO drivers.
Oof, I forgot what thread I was in, because I just meant the buffer size, not the round-trip latency or not even the one-way latency to audio output. Not sure why I said "latency" as that's plain wrong, especially when we're talking from capture in this case.
It's just that I'm more focused on soft synths, and I can get a clean signal out of 64-samples buffers. Granted, that's not what I'd use with any realistic processing (for instance, I use Reaper at 128spl@48k).
While I haven't measured end-to-end yet, I do hope it stays below 20ms. I'm working on a synth-powered rhythm game, and the whole reason I chose to stick with plain WASAPI was to avoid requiring users to install extra drivers and because of Windows 10's low latency stack, with its advertised 0ms capture and 1.3ms output overhead on top of application and driver buffers.
Update: I ran RTL on the budget 2012 desktop and got worse results than I expected at 18ms@128spl for shared-mode WASAPI [1]. For some reason, I couldn't select smaller buffers. On the same hardware, exclusive-mode WASAPI managed 12.25ms@128spl, and ASIO4ALL managed 12.5ms@64spl and 15.1ms@128spl.
Recommending ASIO first seems more like a holdover from a troubled past to me.
These days, I can get ~1ms latency with shared-mode WASAPI on a 2012 then-budget i5 desktop, with on-board audio...
How much mangrove deforestation happens in Tuvalu?
I wouldn't bet on it. They've stated multiple times they intend to eventually provide source-code access, but have always been careful not to call it open-source.
But there doesn't seem to be concrete plans (dates or details) yet, so who knows.
No. Ruby [1] is luxe's main dev.
They just announced today [2] that a second dev [3] officially joined the project.
[1] https://twitter.com/ruby0x1
Cute but disappointing.