Hacker Newsnew | past | comments | ask | show | jobs | submit | NelsonMinar's commentslogin

Is Start9 a well known company? The page by itself seems indistinguishable from a scam, but maybe they have a reputation that justifies their asking for $250,000?


It is not well know but I heard good thing about what they do.

It is very similar to Umbrel [0].

- [0] https://umbrel.com/


I like TopoJSON and have used it in projects. But it's weird to set it up as opposition to GeoJSON. It's a complement. GeoJSON is a general data format meant to replace uses of ESRI Shapefiles and other complex formats. TopoJSON is more of a solution for a particular application need.

Is there much work developing or using TopoJSON these days? I haven't seen much about it in a few years.


To be clear, I'm not suggesting TopoJSON as an alternative to GeoJSON. I like GeoJSON and was loosely involved with the working group that created and updated its spec.

I'm just saying that for the specific task I mentioned GeoJSON or any format such as shapefiles that store polygons individually naturally leads to the "sliver" problem.

A nice processing pipeline is:

1. Convert GeoJSON to TopoJSON.

2. Run the simplification on the TopoJSON.

3. Convert the resulting TopoJSON back to GeoJSON.

The TopoJSON GitHub has tools for each of these steps.


This reminds me ChromeOS has some USB-C cable identification superpowers: https://www.reddit.com/r/UsbCHardware/comments/1pyojjd/comme...

Not sure if it's using the same thing this MacOS thing is doing. In the link the author explains that the cable e-Marker contains a "Discover Identity" message that you can read and display in ChromeOS. Most ordinary Windows hardware can't read it because of BIOS limitations, but Chromebooks can. I'm guessing Macs can too.


How did a bug like this get past their testing?


Given the push to AI/Copilot from MS I'd be impressed if they still did any testing.


CoPilot broke github actions in such a way that if too many requests to start a workflow came in at the same time it would reduce the capacity of the build server's queue until you did a full manual reboot of the build server and completely reset the queue.

Some people are saying they aren't doing testing, I know this to be incorrect in one very important way. When it comes to people, the ways in which a co-worker is going to be wrong are predictable. When it comes to AI written code, there is zero predictability as to what could be wrong.

Trying to test AI written code is like writing code with no try catch blocks, and expecting the application to not crash within 15 minutes of giving to the end user. They will try everything you didn't think to explicitly handle, and when it comes to AI there is no try catch block for subtly incorrect or incomplete logic.


They're at 88% uptime this year. I don't think they have testing.


Microslop®, unmatched quality.


I keep hearing a lot of good buzz about their product. Haven't tried it myself but I mean to.


This video is another good demo: https://www.youtube.com/watch?v=xJLncut79vE


Most old-timers here are familiar with a Prolog-variant: make. Anyone who's struggled over a complex Makefile wishes they had a more sane declarative language!


Every time I read about ancient DNA work, it's about Reich's research. Can anyone expert in the field shed light on that? He certainly seems to have a successful research group. And he's a good communicator, I got a lot out of his 2018 book. Who else should I be reading or reading about?


chromosomal fusion as the explanation for the "loss" of a chromosome pair, in humans.

https://www.johnhawks.net/p/when-did-human-chromosome-2-fuse

also , independent confirmation of observations, are gold for research, however needless repetition of effort is not.

thus when someone is prolific,or uncannily mad about a topic it tends to be dominated by that persons submissions, and often any other contributors are on that lead researchers team.


I'm a little surprised it's not ZFS. Too difficult to add to their Linux environment? That's still a problem here in 2026.


I miss the old days when the choke was built into the (analog VGA) cable.


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

Search: