skysight-inc/HackerNews huggingface dataset:
As a bicyclist, I avoid multi-lane roundabouts like my life depends on it... because it does. Utterly nightmarish experience. This is why I despair every time someone is like "let's build more roundabouts in the US!" No, what you're missing is that all our roads are already too wide and all we get are multi-lane roundabouts, which are worse than intersections. At least at an intersection, I can see that one lane of traffic is already stopped, and know that it would take at least a moment to accelerate before hitting me.
California suspends Cruise robotaxis after car dragged pedestrian 20 feet
See https://github.com/helix-editor/helix/issues/1970 but yeah, other editors do the same thing as Helix here.
MSFT is pretty good with their hardware support.
I recall an article that part of the prep work for shuttles landing in Florida included the usual "Foreign Object Debris" walk through to check the surface for things that might be a problem for the shuttle... but that this often included needing to wrangle alligators (sleeping in the sun on the nice warm tarmac :-)
> but signal and exit by cutting across the outer lane on your way out.

That's how most of the multilane ones are are in my part of the US, and that's what makes them terrifying to me. It requires too much trust that the other drivers are going to do the right thing.
This comment reminded me that AlphaGo exists.

…
I love roundabouts. Driving in the UK is a revelation. You just sort of keep going and driving is a bit more fun. The drivers are also better than in the USA. Which is why I think there’s often resistance here.

Every time a roundabout is proposed near me there’s a vocal group of opposers. I just don’t really get it since in many cases a roundabout is preferred to an intersection in my opinion. But one comment I read summarizes it I guess:

“Drivers here are just too dumb for a roundabout. We can trust them to think.”

And I guess I sort of agreed. Driving in America is weird because so many people do things like passing on the right, not using turn signals, and driving the wrong speed in whatever lane they’re in causing chaos.
Yeah, let's keep this chain of rude and non-informative comments going! /s
This is pure speculation (graphics algorithms and geometry aren't my strengths), but if you were to do this with a set of 3d points, would we get a relationship between delaunay triangulation (pyramidalization / convex hull?) a relative neighborhood graph, and a minimum spanning tree of 3d points, where combining the RNG and the MST would yield between 1 and 8 edges coming out? (at which point, we could use, say, the numpad for 3d gui widget navigation in the meta-verse in the same way you suggest using 4 cardinal directions for 2d gui representations)
Curious what your sample size is on evaluating IC8s. In my experience the small handful I’ve known have been very pleasant people.
> What do people want Zuckerberg to do? Not make bets about future tech?

Future tech like adding legs to ugly avatars?
This is just a small crocheting website, they don't have expertise to make such a fancy feature natively
Setting the record straight on crypto crowdfunding by Hamas
You’re missing the point. This is not a technical problem in the first place, as the poster I replied to did a great job explaining.
wait I thought "traffic circle" and "roundabout" were synonyms
Why would ip-cloaking be necessary if it's your own site?
Hey, thanks for the pointers. Question: are you aware of any materials I can follow to teach kids how to program using Snap!? Snap! has indeed become quite powerful with time, but I struggle to come up with a lesson plan, examples, exercises... whatever will gradually bring kids up to a Scheme-like level of expressiveness and generality.
The just-released Cities: Skylines 2 video game also features roundabouts! They're a huge part of the transportation networks now: https://www.pcgamesn.com/cities-skylines-2/roundabouts

Mini Motorways also had them from the get-go, and they're much more robust than simple 3/4/5/6-way intersections.
Toyota killed off the Yaris and Prius C (I think simultaneously so I assume they shared the chassis or something?).
Checking in from WI here. We started getting a lot of them in the greater Green Bay area about a decade ago. It's better-ish lately, but there are still consistently issues with drivers who don't understand how they work, and there are frankly too many of them located around light-industrial areas. I have no idea how these get approved for those locations: for commuter cars, they're excellent. For LTL trucks, they are highly problematic, cause traffic backups, and due to the nature of those large vehicles, basically the only way they can proceed through them is to wait until there is no traffic at all in any direction, or simply pull forward and hope the driver in the roundabout can/will stop in time to avoid an accident.

It's also worth noting: this are notably more difficult to traverse during fresh snows. While starting and stopping is certainly an issue in snowy intersections, a roundabout introduces a lot of turning, and especially so in cases of spiral ones. Two-lane roundabouts basically have to become one lane during a heavy snow, there just isn't enough grip to safely maneuver one with multiple lanes. And that's with Wisconsin lanes, which are notably large among US states.
I wonder how this compares to e.g. Citus with some triggers and RLS on top.

As this does regional accesses of shared and modifiable data, does Nile implement or guarantee snapshot consistency for cross-shard queries? Citus doesn't have this yet, iirc.

From the docs, I assume Nile does something like the following:

- "smart partitioning" of tables on tenant_id when tenant_id is detected on table creation. These partitions are either region-local when the tenant is located in that region, or foreign tables. (Alternatively, non-local tenant data is replicated with e.g. logical replication/LR, or triggers)

- global tables are replicated across all regions, again presumably with LR

- RLS on the smart partitioned tables, which applies the tenant filter when nile.tenant_id is set.

Do you have any docs where I can read up on this in more detail?

All in all this looks like a real neat project. Congrats on launching.
Reminds me of this fine example of an idiot in a van using a roundabout to attempt orbital insertion:
https://www.youtube.com/watch?v=HyufxcEQPGc
I work at a company that recently tried to shift our (on prem, sharded, 2-metro, 6 replica) mysql deployment to AWS. Any way we sliced it, even after steep discounts, we were seeing massive TCO increases, often up to 10x - the math just doesn't work out for large deployments. It's really a shame that all these companies are forced to write their own (crappy) version of AWS - but price is a feature when it comes to this stuff.
Yes, I actually go to the Mayo Clinic for primary care. It is actually cheaper than the rural doctors and hospital I live near. There is no shopping around for cost. The decision is do I trust the doctor or not. I drive to Mayo because the local doctors make to many mistakes and are not familiar enough with a variety of ailments.
I'm sorry what does any of this have to do with Google's lies with regards to their commitment to cloud gaming? All gaming platforms run at a loss in their early days.

> The cross-section of people with a 10 year old macbook, that want to play the latest AAA title, have expensive high-bandwidth internet, and are willing to pay ~$30+ a month is just not that large.

This is frankly an idiotic summary of what you believe to be the cloud gaming addressable market.
> All successful designs so far have one or two main engines

What a ridiculous falsehood. Every manned rocket to reach orbit since 1966 has used 5 or more engines. Of those that are currently operational, none have fewer than 8.
A better question is whether it’ll have improved or had price increases. GCP has had a bunch of increases lately, and you never know what will be next so you always have to guess at whether you’ll regret locking yourself more to a proprietary service.
> As a driver merging into a roundabout I find I have far less cognitive load.

Excepting for single-lane roundabouts, I find they require a much higher cognitive load for me.
> AppEngine today is wildly different to the App Engine I fell in love with 15 years ago.

I see that as a good thing, it means they are still working on it.
Right, it's trivial to restore the mangled configuration files, but permanently resolving the issue of OS upgrades blasting away user configuration files is on Apple.
https://news.ycombinator.com/item?id=38003497
Quite - I don't have those sensors but I do have madly myopic (sort of corrected) stereoscopic vision and a brain, with 30 odd years experience in it. Oh and I have ears. I generally drive with the window down in town. I can look left and listen right.

My office has an entrance onto the A37 in Yeovil (1) Bear in mind we drive on the left in the UK. Picture yourself in a car next to that for sale sign and trying to turn right. That white car will be doing 20-40 mph or much more. In the distance is a roundabout (Fiveways) which is large enough to enable a fast exit and people love to accelerate out of a roundabout. As you can also see this is a hill so the other side is quite fast because cars have to brake to keep down to the speed limit of 30 mph. That's just one scenario.

Anyway, back to your idea that Tesla FSD (Full Self Driving) ie RADAR, LIDAR etc is equivalent to "me" is debatable. I do have my limitations but I can reason about them and I can reason about what FSD might mean as well.

You assert: "If human vision is good enough, computer vision is good enough." People and computers/cars/whatevs do not perceive things in the same way. I doubt very much that you have two cameras with a very narrow but high res central field of view with a rather shag peripheral view which is tuned for movement. Your analogue "vision" sensors should be mounted on something that can move around (within the confines of a seatbelt). Yes I do have to duck under the rear view mirror and peer around the A pillar etc.

I have no doubt that you have something like a camera with a slack handful of Google Corals, trying to make sense of what is happening but it is really, really complicated. I actually think that your best bet is not to try to replicate my or your sensors and actions but to think outside the box.

Have you ever considered a drone?

Cheers
Jon

(1) - https://www.google.co.uk/maps/@50.9471642,-2.6382854,3a,75y,...
>The reason why they keep it is because there is literally nothing else interesting about the place.

Rude. ;0P
> I'm a big advocate of rapid prototyping as a _huge_ business lever, because the ability to try out ideas quickly, to easily reconfigure things, is the key for time to market. You can quickly see if something is going to fly or not.
And that's where the advantage ends.

Too many businesses aren’t even properly utilising that key advantage. They’re moving servers to the cloud but still using their outdated development and deployment processes, and things move just as slowly in the cloud as they used to on prem. They know what Infrastructure as Code means, but only as separate words.
This is a technical problem, not a legal one. Don't take your phone.
ProtonDB started with a lunchtime reddit post and a public Google Sheets link I seeded with three of my own tests. Came back from work with a thousand rows in it. In a few weeks I built a frontend around it. The 30k row data migration was brutal but in hindsight was absolutely worth it. AMA.
No sale. Too much complexity and too many side-effects.
We had to purchase/lease HP storage servers with 10x the storage we needed for our photo startup in 2006. The lead time to get a server was weeks so there was very little elasticity to respond to non linear growth.

Would have been a lot easier if we had S3 (launched around this time, no one really knew about it or what it was).
I often hear people form DeSantis's party pushing their right to discriminate and spew hate against LGBT folk based on "free speech principles". Even forcefully arguing for free speech on this basis.

When you say conservative, many people would think of a Principled person who sticks to their Principles and Values.

This is a good example of how that is often not the case. If anything, I've found many conservatives to be hypocrites with loose values that change and adapt depending on the situation. This is a perfect example of that, blocking the free speech of this student group.

Its free speech, as long as it's speech they agree with.
this is pretty smart, i didn't realize the hotspot tells you how many connections there are although i don't really use mine. my mind went straight to bluetooth pairing.
I think the second "gotcha" is that even at 83 microns, that particle size is likely unsafe. That's about the size of gypsum dust used in drywall and you can't cut or sand or do anything without PPE for long without serious health consequences. Make it any smaller and it'll be well into the asbestos size range, which would probably be carcinogenic based on the mechanical damage it causes alone (a lot of nanoparticles are toxic for this reason). That's safe in a controlled industrial environment with everyone using fitted respirators but spread out on fields exposed to wind, near residential areas? Dumping that much fine dust everywhere would probably create a similar hazard to the dried out beds of the Great Salt Lake or the Salton Sea or Blackrock Desert* except everywhere there is farmland.

It'd have to be combined with a binder to form much larger particle sizes so that the natural weathering safely exposes the olivine slowly over decades. I suspect that once one does the math on the whole lifecycle, it's net carbon positive only after decades if it is to be done safely.

* People who have been to Burning Man can testify to just how much trouble dust that small causes, not to mention the frequent dust storms with zero visibility.
I thought "find my" on newer iphones could do local non-cellular location services, like airtags.
datacenter network speeds are ~400+Gbit (between data centers) and in the Tbit range within data centers. A typical server now has a 10Gbit NIC.
Just adding to the already rich discussion an anecdote about stop signs preceeding a round-about: worst of both worlds.

Example: https://www.reddit.com/r/bayarea/comments/10pihgk/roundabout...
My database technology startup, Fireproof, recently hung out a shingle for custom app development, primarily as an adoption tactic. If we really do have the most productive tools for front-end devs to build data-driven apps, we should showcase them by writing code for real-world customers. Over time we expect services revenue to be a smaller slice of the pie, but if we can make creating the first round of social proof into a financially sustainable practice, we can scale with more confidence because we know we built what customers want. We just launched this today, so you'll have to follow up if you want to know how it goes: https://fireproof.storage/service-and-support/
The metric we are interested in is cost relative to self-hosting on similar hardware.

So you can't factor in things like inflation and hardware performance, which equally made self-hosted solutions cheaper.
It's essentially creating states/variables then garbage collect it upon completing. There are several things you can do:

Remember it in your brain: It's like let the state occupying one of the 16 registers in your brain. Later it will automatically offloads in the hard disk in your brain but there's a chance it gets lost or cannot be recalled reliably. Not recommend. But I do this more recently because I realised I don't have to do everything.

The stateless approach: Do it immediately so you don't need to bear the state/variable. Even though sometime it disrupts my current tasks, I find this approach is surprisingly relieving - less debts. Just like software engineering - minimise states because they're evil.

External storage approach: Write it down on paper or an app. There are trade offs between the tool you're using, but the key is to minimise the cost of your moves.

For pen and paper I tried different configurations until I can always comfortably carry them in my pocket.

For digital approaches I'm currently shovel things to Linear. Make sure you're fluent with shortcuts so you can create tasks and jump around like a breeze. I also use Arc browser and pin it in the third slot so I can jump to Linear with <Cmd-3> without even thinking about it.
Fair point. Maybe I should upgrade from Skippy before I turn 40.

Weird aside, my mother burned out her immersion blender attempting to reconstitute a jar of natural peanut butter. I now stir a few jars for her when visiting.
I’ve noticed something similar, just a half hour of noodling on the guitar/bass while working in the middle of the day and I type way faster and correctly afterwards.
So what happens if someone figures out a simple way to bypass immobilizers?

You can always look back at something and say that it's dumb or that the fix was obvious, but back when those cars were made, they were cheap, and theft wasn't as big of a problem. Did you notice that they weren't getting stolen until the flaw ended up being broadcast all over?

Just about every Honda from the 70s through the 2000s can be easily stolen. All you need is a key from any other Honda. I've unlocked my Hondas and my friend's with my other Honda's keys tons of times. We even moved my friend's Nissan pickup across our high school campus with my other friend's Sentra key. Should we go back in time and go after them too? There are tons of easy tricks to steal just about any car, this is just the one that got publicity.

I mean, if they should have designed them like this, why did insurance companies choose to insure them in the first place? They are the first people who should be aware of the anti-theft measures in a car, and charge accordingly. Instead, they look back and go "woops, we didn't know this would be a problem, so now we're dropping Kias and Hyundais" It's literally their job to assess risk, and even they didn't think that the missing immobilizer was a problem.
>there is no confusion

Maybe not if you grow up with it. But there certainly is if you are a British tourist, used to always giving way to the right.
It doesn't need to be about money. Think about research.

They do a lot of it. And honestly? They seem quite more open about it.
I have never seen anyone go the wrong way around a roundabout, and I've never heard anyone tell me they've seen it. It's so rare you can ignore it.
sounds lit
So, there is no security feature that prevents a phone from connecting to a cloned wifi network??
I love this article. I’m about 10 years away from retiring and Elixir/Erlang have been the highlight of my software engineering career because of things like this.
Why not run it on your main OS? Otherwise, Docker is fine.
I didn't say they did it wrong, I asked a question. It wasn't a rhetorical question.

Anyway, this point might be moot because dav1d has released several versions with further NEON optimizations after the paper

https://code.videolan.org/videolan/dav1d/-/tags/1.1.0

https://code.videolan.org/videolan/dav1d/-/releases/1.2.1

https://code.videolan.org/videolan/dav1d/-/releases/1.3.0
> Also, on the small side where you have traffic circles rather than roundabouts, those also suck.

Interesting. Can you elaborate? We have a few of them (and growing) by me and they’re fantastic as far as I can tell. No stopping every block for stop signs, I’ve seen landscaping truck with trailers sneak through them fine, and it’s so much easier on a bike or while walking. What’s the downside?
Perhaps my biggest critique is that crates.io has no namespacing. Anyone can just claim a global and generic package name and we mostly have to deal with it (unless you avoid using the crates.io repository, but then you'll probably have more problems...). Some of these globally-claimed generic packages are not really the best package to use.

Maybe it was a reaction against the Java-style reverse DNS notation, which is verbose and annoying, but a more GitHub-style user/group namespace prefixing package names would have been the nice middle ground.
You want Support Engineers who are up to speed on your code review processes and standards and given access to commit "straightforward" bug fixes. They exist :)

https://gitlab.com/gitlab-org/gitlab/-/merge_requests/125249
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/131316
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/131469
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/130988
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/132806...

From there, you need to build a culture that is welcoming of "strangers" contributing code. You get these two things, you get nits and gotchas fixed directly from pain points customers are having, while product engineering is (mostly) focusing on feature dev.
As I'm in the terminal most of the time, I started using todo.txt [0], but I haven't used it enough to tell if this is *the* solution for me. Curious if others use this too and can stay on top of things with todo.txt

[0] https://github.com/todotxt/todo.txt-cli/wiki/User-Documentat...
A 5% chance of needing to do a migration in 10 years is very small in comparison to other technical risks.

And lets be clear, this is not a catastrophic risk; your contract with GCP guarantees they will not discontinue services without 12 months of notice so you will have time to do an orderly migration unless Alphabet itself goes under.

I am a GCP user; I have found their offering (actually having GPU quota) significantly better than the other clouds and GCP shutting down does not keep me up at all.
We unfortunately have three vendors (AWS, GCP, Azure) at my company because of acquisitions and the cost involved to consolidate.

I am part of the central team that manages the provisioning users and accounts and billing.

AWS is miles ahead of how we can express what we want in accounting.

AWS reps are much much more knowledgeable and a pleasure to work with when it comes to billing.
Accurate and Efficient Post-Training Quantization for Large Language Models
suprisingly often in real situations when I just want to get the columns of a table with no data I have done

select * from table where (1=0)
Go made a great decision to namespace packages via this Github style.
Out of curiosity, is there a list of built-in non-deterministic SQL functions?
ooooh, micrometers. I was thinking pebble sized. I wouldn't call it crushed, it's pulverized powder (polvare which is powder in Italian, you see it in reference to minerals in wine vineyards)
One of the things that we did at Kapwing (https://www.kapwing.com) was manually edit videos using our own platform and sharing these videos with bloggers to try to convince them to use Kapwing. We could create a relevant video from an article that they wrote, and then share them the link to the project so that they could edit it directly with our tool.

Another random thing we did was try to make chalk posters on the streets of SF. We chalked our logo out in front of the 4th and King Caltrain station so that tech people would see it when coming out of the station. Unfortunately, that only worked for a day though, because the SF crews are very good at powerwashing the sidewalks.
They’re often worse in heavy traffic situations. Especially if you have two entrances that feed heavy traffic into the roundabout at peak times, the one that has to yield can end up basically locked out of the flow.
"Rust has its warts". Interesting terminology.
It really all depends on how much you want to spend in retirement. But, yeah, 1 million at 4% is 40K before taxes. The next thing you have to do is decide if you want to assume SSI will be around at your retirement. But if not, can you live on 40K per year?