skysight-inc/HackerNews huggingface dataset:
May be down to many aspects and insurance certainly would be a factor in gauging risk/costs for the number crunchers when creating budgets. Given hurricanes tend to fall into the act of God clauses and Terrorism tends to fall into its own special category of exceptions/coverage extra's.

That along with overall impact upon society and fiscal impact. Does get down to hurricanes you can't prevent, only clean-up and terrorism you have a better chance of preventing - also when people die from the later - they are more inclined to place anger at the government/administration over hurricane victims.

Terrorism - case of dammed if nothing happened and you spend money, and dammed if something does happen irrespective of how much money spent.

Certainly - would people feel better if the government spent less on terrorism and just put it down to something people have to just accept could happen and part and parcel of living in a city! That won't traction well with many people I'd say. Yet the people have that mentality towards hurricanes - they accept they will happen, unlike terrorist acts and that kinda see's why budgets are the other way.
12 hours transatlantic is probably worse than coach (or premium coach at least) transatlantic in 7 hours for most cases.

With these specs (which are completely fictional at this point), it's the size and cost of a light-jet with the speed and range of a mid-sized jet, which is a under-served niche with the increasing numbers of people in the "very wealthy, but not quite embarassingly wealthy"
You're twisting my point. I could as well turn it around and ask you these:

You really think everybody who's not a journalist and reports on China, must be a liar, and cannot possibly be genuine?

You think all journalists are unbiased and truthful?
Tell that to the people who died in New Orleans in Katrina due to ACOE's terrible levees.
> it's also a really complex one!

No, it's a very simple one, so much so that it's erasable: https://news.ycombinator.com/item?id=24293611 And still it is probably the most complex aspect of Zig.

> Zig is cool, but I hoped the “generics are too complex of a feature” meme would die now that Go is getting generics, and I'd be really sad to see come back…

You've misunderstood me. Generics are a good thing -- if that's all you have. But if you have generics and procedural macros, it turns out that you can do the work of both with a feature that's simpler than either. The capability generics add is a very important one, but given that low-level languages need another one as well, it turns out that generics can be subsumed into that one without being a separate and additional construct. Zig has generic types and concepts/typeclasses; these just aren't atomic language constructs.
ad hoc networks
Or emotional labor. But yeah, setting up k8s would not qualify. I thought there was an older version of the same general riff in Fast Company, which I can't find right now, but here is a blog post about a version that appeared in Free Prize Inside:

https://educationinnovation.typepad.com/my_weblog/2010/06/ed...
This clause like many others have been abused to the point there the literal words do not mean anything, this is the so call "living document" interpretation of the constitution, one that should be rejected as it sets in place a "standard" that the words mean what ever we choose them to mean

There was an Amendment process put in place expressly to prevent the type of "reinterpretation" you are advocating for, if we the people desire the US Federal Government to provide us with Internet then we the people need to pass an constitutional amendment declaring that power
Was somewhat janky but quite impressive nonetheless. Whats not as clear is .. how easy is it to make this UI in webflow. I can easily imagine making this in React.. how much less time would it take in webflow? Or is the appeal purely accessibility to non devs.
Viburnum Tinus Fruits Use Lipids to Produce Metallic Blue Structural Color
Even worse than undiscoverable features are land mine features, where some subtle gesture triggers a wild and unwanted mode change. Extra credit if the mode change is hard to get out of.
If no light falls onto the detector then there is no blooming. And of course there will be diffraction from the shutter edges as well, so engineering it will be quite a challenge (one can take hints from coronographs). If the satellites does end up on the sensor then the dimension of the streak depends on the optics, how bright it is, the used detector, plate scale, etc. (if you are extremely unlucky you might have internal reflections too and they might end up who knows where on the detector - optics is hard).
My older child is 11 years old, and since a few years before she was born, everyone we knew in India had been naming their children starting with the sound of "Aa" ... We know quite a few kids named "Aarav" and "Aadya" among others. So any names with that starting sound were immediately discarded. We wanted her name to sound significantly different from all contemporary names, and we decided that the best way to do it was to go retro. So "Surabhi" is what we chose. It has a very nice meaning, and it's just sufficiently old to be fashionable again. And it also reminded us of a favourite TV serial from our childhood.
> What has always suprised me about open source software is that the source is always 'out of band'

From "Open Source is not enough" by Adam Spitz[1]:

The Open Source movement is great, but it doesn’t go far enough. […] When I feel the Urge To Tinker, only rarely does it feel like a loud voice shouting in my brain with enough energy to propel me to find the website and download the source code and figure out how to find the part of the code that corresponds to the thing I’m looking at on the screen and make the change and restart the program and retrace my steps. Much more often it’s just a quiet voice mumbling, “Hey, it’d be kinda neat if…” and then I think, “Well, it’s Open Source, I guess I could go download the source code… but… meh, it’s so far out of my way, not worth it,” and the urge fizzles out. I think that a lot of potential human creativity is being wasted this way.

> Of course I realise that this workflow is not technically possible in the way software is currently built, but it does seem worthwhile in the future

I've been thinking a lot about this and working on it. On a technical level it's more possible than it seems—even with "conventional" toolchains—but the primary obstacle is going to be social rather than technical. Funnily enough, GitHub's popularity and its measurably less-than-optimal workflows actually serve as a preview of how difficult it will be overcoming stalwartism from people who are technophiles first and only think of productivity as an nth-level concern—somewhere at a lower priority than social media presence and ginning up demand for the skills and practices they've alrealy invested in.

1. https://web.archive.org/web/20151016184630/http://adamspitz....
Awesome! Seems very easy to add to Next.js/Gatsby websites.

Btw you can migrate from Medium to Jamstack with this Stackbit tool: https://www.stackbit.com/medium/

Seems like a great combo!
What about "deep" work? The kind of work that requires you to understand the fundamentals of a complex system to be able to simplify/modify it for the better.
Neat! One nitpick: never do a voltage switch like that with a toggle, always use a slider. A toggle is way too easy to accidentally trip.
Rewrite it in rust is not mature reaction from rust community. It is similar to arch linux btw boys you see in Linux communities.

And GP is right, you rust folk talk as if sum types are silver bullet. And you people also talk as if rust invented sum types (though you people don't imply it).

You folks talk as if cargo is the best package management solution that exist.

You folks talk as if web of hundreds of dependencies written by enthusiastic youngsters is not a problem for a language priding itself on safety properties (the attempts like crev don't get the attention they deserve).

You folks talk like the memory management overhead of rust is not a problem for creating average CRUD webshit.

You folks talk as if rust automatically guides you towards correct programming patterns, when that is out of necessity to facilitate static memory management. The business logic is not at fault here, neither is rust.

Some folks in the rust community frequently bring virtue signalling politics into programming language related medium.

Rust is a well designed systems language and deserves appreciation for bringing Ada / Cyclone / ATS' good parts as a usable language. But the community is ruining its image.

Plaudits to all involved.
The proposed battery has a power output of 100 microwatts. You can probably get more output with a tiny photovoltaic cell (like the ones on calculators).
Overpopulation is not an issue.

In practice, the most effective route to limiting population growth has been shown to be making people rich.
I don't think it's done much for the Boris Johnson government here in the UK:

https://yougov.co.uk/topics/politics/trackers/boris-johnson-...
it would blow my mind if you tell me you know a company that has written a literal check for a security clearance in the last twenty years.

i suspect that cost barrier is more the government saying "we aren't paying for it, you need to find someone that is already cleared."
Balaji Srinivasan: Living in the Future
I think we may be seeing an organizational issue at work. The job of a design department is to produce design. If there isn't enough new stuff to design, they will redesign old stuff. This serves to advance the critical goal to the design department of justifying their continued existence.

The number of designers who will march up to their VP and boldly declare that all the company's apps are just fine and don't need any kind of redesigning is small.

You get a similar thing any time a development team runs out of feature work or actual stress points in an application they maintain. They wind up reworking the thing mainly to have something to do to justify the continued paychecks until the business thinks of an actual reason.
It doesn't mean any of those things. It just means not making the updates automatic. Make your auto-update just say "hey your version is no longer getting updates, you can get the new version at this link"
This piece is excellent advice. It’s way better to retain integrity and build on that than to dissemble and fudge things, if only because maintaining separate realities is a tax on your brain.

However, the title is completely false.

Anyone who has been around the industry knows that both founders and executives can achieve success through exaggeration, distortion, “acting as-if”, “fake it till you make it”, dissembling and outright lies.

These things create low-trust toxic environments, but people can still make a lot of money in those environments.

Don’t engage in these behaviors. They make the world worse for both you and everyone else.

But don’t gaslight yourself into thinking that people are not successful because of them.
Good advice for any voting year: get a checklist and check things off in advance so that voting is extremely convenient when polling time comes.
That might be true, and may involve backchannel negotiations. But Apple didn't hesitate to revoke Facebook's developer certificate (for internal apps) and make Facebook employees scramble for a day or so because of the "VPN" app tracking fiasco early in 2019. [1]

[1]: https://www.theguardian.com/technology/2019/jan/30/facebook-...
The gist of the article is that protocol you want already exists and is integrated into git- email. Everything that people complain about that workflow (barrier to entry, initial setup and difficulty to track) is merely because the tools are primitive and unpolished. We wouldn't be considering the Fork-PR workflow if even a fraction of effort that was spent on improving the email workflow tools. There is no reason why email workflow can't be easier than Fork-PR. Consider this - sourcehut is only a pretty interface to discover projects. You don't need to create an account to contribute to the project. You can collaborate even if everything other than the mailing list is down (even that can be overcome). How can Github/lab surpass that even if they bolt on a federation protocol on top of their PR-Fork model?
> Jesus is not a saint.

Good to know, but the overall point is the same, I think. He was a person who is (obviously) very important to Catholicism, and therefore the name has an equivalent in every widely-used language.
But Gitlab is its own walled garden (albeit an open-source one). What we'd ideally have is a platform-agnostic PR protocol. Sadly, we're not likely to get one.

That being said, I agree that "let's all use plain-text email" isn't a very good alternative. It's perfectly possible to use Gitlab or Gitea and have the web UI experience without marrying yourself to a proprietary ecosystem.
SMTP is terrible, especially for people with corporate accounts behind firewalls. I've contributed to linux in the past and dealing with corporate IT was a miserable experience and saw lots of other kernel developers waste their time fiddling with SMTP parameters.

Those same firewalls can pass https or git+ssh just fine, it "just works". SMTP is not worth dealing with.

Email is also not very good as a forum, for example you can't edit your posts for spelling fixes, archives are unreliable and hard to browse and it's difficult to map git commits to reviews.

It's also wrong to claim that linux code review is somehow "distributed", it is very much centralized on a couple of mailing lists servers on vger.org.

It would be much better if kernel maintainers kept their trees on github and started accepting PRs.
Lack of competition. Lack of people who understand or care about UX. For example, a typical enterprise software company will hire programmers who are both skilled in programming and have domain experience, i.e. a financial programmer for a financial industry app. This is because they believe, probably correctly, that understanding finance is more important for their developers than understanding how to make beautiful animations play at 60fps.

There's a lot of other problems. "Enterprise" software often comes from companies that aren't actually software companies, in the sense that they aren't run by the guy who wrote the first version of the product. They're run by non-tech people who hired some developers to build their idea. These people typically create large and bloated product and project management organisations that try to convert programmers into replaceable cog wheels that convert JIRA tickets into code commits. They often dream of out-sourcing their devs entirely and would love to do nothing but sit in the middle collecting fees without needing to write software. They certainly cannot judge the quality of the work produced, even by looking at the user interface. Maybe they have some vague feeling it could be better but they aren't going to dive into the detail and figure out why or how.

Developers know this and have minimal loyalty to the product or organisation, so whatever work is done is always minimal effort work. If the ticket can be marked as done they move onto the next one.

Successful consumer facing software firms are often quite different. They're run by someone who uses their own product, at least sometimes, and who probably made the first version so they care about the details and know what's possible. They hire developers who are NOT domain experts, on the assumption that if you need expert knowledge to use the app you're not making consumer software, so they hire people who have a proven track record of creating beautiful and easy to use UI. What the UI exactly does is not so important. They tend to trust developers more, in my experience, because they know a small performance or UI edge can be sufficient to differentiate them in the market.
Terrorist attacks were responsible for at least one expensive war.
Just because others have copied the interface doesn't make it 1) portable 2) part of the standard 3) a protocol. You'd ideally want all three for a viable alternative to email-based patches.
You act as if all that damage could be prevented by FEMA.

The point is there is only so much you CAN do to prevent damage from a hurricane but there is a lot you can do to prevent a terrorist attack.
Depending on the app, it's just sound security. On a jailbroken device, you cannot assume any of the OS safeguards are still in place. On a stock iOS device, there's pretty much no relevant malware that could be on that device. On a jailbroken device, all bets are off.
C++17 zero-cost key value maps using POD objects as backend
"Researchers" is perhaps saying a bit much. It is an art school that is doing this, so it probably counts more as an art project.
It's just images and videos, like InVision or other tools like that. Click button -> change / overlay an image or play a video.
A similar thing happened when someone made did this promoting the YouTuber "PewDiePie"[1]

1. - https://www.forbes.com/sites/thomasbrewster/2018/12/03/a-hac...
Well, on one hand it looks like WebFlow is primarily geared towards UI versus complex logic.

OTOH I'm willing to bet that if someone built Civ 6 in a no/low code tool the API costs would be astronomical.
Show HN: Reading Reminders – Readwise for your notes (snippets to your inbox)
It's propaganda for liberal values as long as they serve the interests of the US. Allies get a pass, and liberal enemies of our allies will be criticized.

Bin Laden was a good guy when he was fighting the Soviets.
> Bad disaster responses can make administrations look pretty bad.

Whether disaster responses are considered good or bad depends largely on which narrative the media select.
Online isn't real-life. You can test in a VM, but it will never be the same as testing on actual hardware.

Even my craptastic company gives me a bunch of devices to test on. And I very deliberately specify very low-end versions of the machines so that I can test against worst-case-scenarios. It's a bonus that sub-optimal hardware is cheap as chips.

My favorite testing device is a $20 burner phone I picked up in the supermarket checkout aisle. If the web site works on that piece of poo, it'll work on anything.

Right now I'm waiting for UPS to deliver an old iPad from Alaska that the IT department bought for me off of fleaBay, just so that I can test on sub-optimal actual hardware.
Standard library documentation is indeed clunky as it is auto-generated for the most part. This is something the community has been working on improving but it isn't a priority at this stage in part because the standard library undergoes breaking changes pretty frequently right now.

Optional and ErrorUnion are a tiny bit redundant in that one could represent the Optional as another value in an ErrorUnion, and that might even happen as an optimization step in the case of ?!/!? types at some point in the future, but they have very different handling in the language as they are used for very different things.

I personally like that Zig doesn't bother with "strings" at a language level at all and just considers everything as arrays of bytes. String handling is a complexity nightmare and I feel that Zig wisely chooses to be simple instead.
I think you're comparing apples and pears when you talk about Maps. There's a clear use case for scrollbars on vertical documents (i.e. most of them), and even when viewing something in an infinite scroll, so you know where you are when scrolling back up. (Although don't get me started on the UX of infinite scrolling!)

Edit: Thinking further about this, the affordance for maps is a change in the cursor to a grabbing hand. You have to learn that, but there's a clear visual difference in the cursor to show that something differnt happens there.
This might be a problem, but if you're careful to make use of transparency, axis scaling and random jitter (for integer or categorical values), the occlusion issue can be overcome.
This probably takes us 1 step closer, right? Normalization often a first step to recognition.
A witness is proof, unless you have a specific reason to believe the witness is unreliable.
Thanks! It really depends on the project. If I'm joining an existing project then pricing specification is very complicated as you don't know the system architecture. In such cases I would opt in for an hourly project.

When architecting a system from scratch it's a bit easier since you don't deal with legacy systems at the beginning. Then when doing specifications I tend to divide the system into parts: actuation, sensing, logic. Then depending on the application I try to choose the best systems for doing the job.

For example if the robot is meant to be used in an agricultural context you know you need some kind of global localization (RTK GPS is probably best), usually you will need an IMU as well (this one will depend on the platform, budget etc). Then if you are expecting some occlusion (e.g. treetops) you might start thinking on what will happen to the GPS signal and what other sensors to add.

I do similar considerations for the actuators and software logic, trying to think of all possible scenario in a representative environment. From my experience if the work is fully remote it takes between 30 minutes to 1 hour just to discuss the environment, allowing me then to propose the best systems for the job.
> it's for shitty low-end laptops that still to this day have 1366x768 displays.

We had scrollbars on 640x480 both ways and liked it. Even SGIs with 1280x1024 monitors had scrollbars, and it wasn't a burden that some folks today seem to think it was.
I don't think the program itself needs elevated privileges, because it only reads from stdin and writes to stdout. I am running the interception tools as systemd service, though. I think the Intercepton Tools themselves need elevated privileges; I mean, it's kind of key logger if you think about it.
True in the limit, but they can easily be funded and create the impression of success for a long time, and even exit before that outcome.

Theranos, and WeWork would be good examples.
You can get back to 1980's tech easily enough if you have 1970's tech. And so on all the way back to about 1920. Whatever you have + the knowledge remaining will allow you to rise up the ladder a little quicker but not that much quicker because you still need to go through all the motions in between. Skipping steps is really hard, most progress is incremental.
The power lines were, to a large extent, built with U.S. money after the war. Many rural areas have seen little infrastructure investments since then.

Anyway, if governments, businesses and individuals care enough then it's easy enough to develop that infrastructure now. The satellites will come down in a few years.

Who volunteers to tell Musk?
They didn't have corporate backing.

They didn't have aggressive marketing or zealous community.

They didn't have massive influx from ruby rails or javascript webshit crowds.
As an aside, kudos on the document format —- very reminiscent of Sun documentation from back in the day. (I still miss FrameMaker.)
Two metres or one: what is the evidence for physical distancing in Covid-19?
Additional context:

https://news.clearancejobs.com/2020/08/26/tesla-insider-work...

https://www.justice.gov/opa/pr/russian-national-arrested-con...
"You can work long, you can work hard and you can work smart, but you can only do 2 out of 3"

-- source unknown, common among programmers on usenet in the 1990s
I'm an American and had a vasectomy and one of the bigger reasons was that I don't want have kids that continue to contribute to the destruction of our planet by just being regular Americans. I felt like it was the biggest single contribution I could make for environmentalism.

I also ride an electric bike, live in the PNW where I use barely any heat or AC, limit meat and dairy intake, and generally just don't buy stuff unless really needed.
Option d) technology and good government policies enables a low/no carbon future.