skysight-inc/HackerNews huggingface dataset:
Everyone disagreeing with you is only assuming improvements to drones and not the counter-drones (or the counter-counters you mention).
Based on my experience in the space, I can say with some confidence that there is very low brand or reputational risk (or it is so low as to be immaterial) with regards to a breach. $1M-$3M in most cases, which is cost of business (notification campaigns, buying credit monitoring, etc).

Edit: Your examples are outliers, based on the data, and those costs are not brand and reputational, they are settlements or fines (which are rare). If you want to move goal posts, that's a choice. No one is going to stop using Equifax for consumer reporting data or Target because of their cybersecurity posture (ie brand and reputation damage).

https://www.ibm.com/reports/data-breach

https://www.vox.com/the-goods/23031858/data-breach-data-loss...

https://www.idtheftcenter.org/post/itrc-sees-third-most-data...
It's almost as if it was an intentional artistic choice in phrasing... /s
You could optionally ship object files, along with a script or Makefile to relink them, as a separate “link kit”-I believe that would comply with the letter of the LGPL. 99.99% of your users would never download it, but so long as you make it available to them to download, you’d be complying with your obligation under the LGPL.

But of course, this is extra work just to comply with the letter of a license. If they switch to MIT, you don’t need to do that. Indeed, it appears you can already swap the license to MIT provided you remove certain features (such as 32-bit ARM code generation and COFF support), and you might not need those features in your use case

> But as I said you will lose technical control of the project, if not legal control of it, by distributing the source

Proprietary software is sometimes shipped to customers in source form: once upon a time it was very common-prior to 1983, it was standard for IBM to ship source code to their copyrighted mainframe software products to customers. A lot of other products used to offer source code, sometimes for an additional license fee (e.g. AIX, OpenVMS, pre-open-source Solaris). It still isn’t unheard of for products targeted at professional, embedded or enterprise use - e.g. many commercial ERP systems are shipped, maybe not with complete source, but with source for large chunks of the business process code. Many of the background processes (such as payroll) in PeopleSoft HRMS are written in COBOL, and Oracle ships the COBOL source code to them, and customers are allowed to modify that code and recompile it (although of course Oracle strongly discourages that, especially nowadays, it is still permitted)

A closed source product is still closed source even if you ship the source code to paying customers, so long as the license prohibits them from sharing that source code with the general public
uBO has had this feature for awhile, since 1.34.0 (or 1.25.0 in advanced settings).

https://github.com/gorhill/uBlock/wiki/Dashboard:-Settings#u...

I think that's around 2021 time frame. FYI.
That sounds a lot more promising!

Which brings in even more questions. What is the performance of these multiplayer experiences? Can I have 1000+ users all connected to the same chat session? What about 10,000?

(these numbers might seem high, but they're what I'm expected to deliver in my day-job)
Thank you so much for pointing these out! Yes, it's react native. And thanks to your comment, I am also working on getting my account setup on open vsx
Subordinate Latin
Part of "making them pay" is making all of the companies pay, which makes your argument sort of moot. If not all companies are being made to pay, then you haven't done anything.
Japan's entire countryside is littered with cheap or abandoned houses.
thank you! I'll release the code for the VSC Extension soon.
"So what?"

So some of the "successful" people in our industry never read anything other than technical books. And if they have read some, they never understood anything.
Sodium ion batteries are widely available now. We haven't had a new battery you can actually buy in like, ten years or more.

Meshtastic now has way better encryption from what I hear.

The CH32V 20 cent riscv chips seem to be Arduino ready and somewhat mainstream.
Sure, they might be inept now, but wait until they're desperate!
Thank you, this is a TIL!!
I looked into MISRA specifically for my previous job and Rust effectively complies with most of it out of the box, and what's left is either inapplicable or not difficult to catch with further tooling.
Anglosphere military I would guess. Somewhat of a shared culture unique to those veterans.
OpenBSD 7.6 release artwork by Sue Doeksen

https://www.openbsd.org/images/LifeIsButADream.jpg

https://www.openbsd.org/images/puffy76.gif

https://www.openbsd.org/76.html
joking aside, i do think that as AI continues to pervade public consciousness, we will start to see some creators market their products as being "AI-free" or somesuch, for better or worse. It's like lemon market virtue signaling.
This blog post is so scattered
>then you're like, ‘Wow, this is amazing, but my inbox is full.'”

This seems like the core cause to me. If the maintainers are tired then they won't have as much time or energy for mentoring new contributors which means we will have less new contributors as time goes on.
> Which is a very valid concern. If that's your point, I apologize.

It's a valid point to argue, but it does need to be argued, not assumed.
I’ve seen monumental engineering effort go into managing systems because for one reason or another people refused to use (or properly configure) autoscaling.
It's part of the guidelines https://news.ycombinator.com/newsguidelines.html

> If the title contains a gratuitous number or number + adjective, we'd appreciate it if you'd crop it. E.g. translate "10 Ways To Do X" to "How To Do X," and "14 Amazing Ys" to "Ys." Exception: when the number is meaningful, e.g. "The 5 Platonic Solids."

> Otherwise please use the original title, unless it is misleading or linkbait; don't editorialize.
>Imagine the drone just sitting there listening for a helicopter to get close enough

Imagine a drone which outputs the signature of an attack helicopter to draw out that loitering drone and then destroy it, leaving the space open for an actual attack helicopter to swoop in and do its business.
Apps weren't the iPhone's first mover advantage. It was a quality data plan, browser, and hardware to support them.
A lot of people in this thread seem to think OP was suggesting that geoengineering is a possible way forward right now, when they were just positing it as an example.
Wrong.

Heartland Payment Systems - Although the company did not go out of business, it suffered significant financial losses from a major breach in 2008, leading to over $110 million in settlements and fines. This incident severely damaged its reputation and operational capacity.

Target - The retail giant faced a massive data breach in 2013, which compromised approximately 40 million credit and debit card accounts. While Target did not go out of business, the breach led to substantial financial losses, including a $18.5 million settlement with state attorneys general.

Equifax - The credit reporting agency experienced a breach in 2017 that exposed sensitive information of about 147 million people. Although Equifax remains operational, the breach resulted in over $700 million in settlements and significant reputational damage.

MySpace - While MySpace did not directly go out of business due to its data breach in 2016 (which affected 360 million accounts), it lost significant market share and relevance, ultimately leading to its decline as a social media platform.

FriendFinder Networks - This adult entertainment company faced a severe breach in 2016, affecting 412 million accounts. While it has not officially declared bankruptcy, the breach contributed to its ongoing struggles in a competitive market.

Ashley Madison - The dating site for extramarital affairs suffered a data breach in 2015 that exposed the personal information of millions of users. The fallout from this breach led to lawsuits and significant reputational damage, severely impacting its business operations.

NortonLifeLock (formerly Symantec) - Following a series of breaches and security issues, the company faced declining revenues and market share, leading to a significant restructuring and changes in business focus.
Because, sadly, a lot of system designers want to believe they have a way around it.
This is an opinion from a real intellectual https://youtu.be/6qnWqlYMipM?feature=shared

And this is the article that he is mentioning https://www.currentaffairs.org/news/2018/03/the-intellectual...
Yeah, CAP is about the best possible behavior a system can have but you can always do worse.
The thing is, not everyone is an engineer so to normies it's not simple. easy or efficient. There's a reason why people like windows.
> The value is now stale, but it was correct at some point between the read starting and the read finishing, right?

Not necessarily. Maybe both versions of it were from partial writes that were never committed, so your invariants are violated (if we're talking about e.g. a credit account A and debit account B scenario).

> That can happen with any read. Even without any partitions. Can't it?

Depends on your isolation level. If your system has serializable transactions then it's supposed to give you a history equivalent to one where all transactions were executed serially, for example.
Warriors and Worriers (Benenson)

The Prince (Machiavelli)

Beyond Good And Evil (Nietzche)

A History of Western Philosophy (Russel)

The Fourth Turning (Strauss, Howe)

Also, Discourses on the First Decade of Titus Livius (Machiavelli) is a fascinating read on human political machinations (albeit fairly slanted by Machiavelli's personal views)
.NET's Task<T> + the state machine box for it emitted by Roslyn start at about 100B of heap-allocated memory, as of .NET 8/9.

The state machines generated for those by F# don't seem to be far behind either (I tested this before replying, F#'s asynchronous computations aka async { } appear to be much less efficient however so the guidance is to avoid them in favor of task { } and .NET's regular tasks).

Notably, BEAMs processes come with their own per-process GC each, which is going to add a lot of additional cost every time a new process is spawned. In a similar vein, Go's goroutines pre-allocate quite a bit of memory for their virtual stacks (60 KiB?).

.NET's tasks, as sibling comment mentions, are stackless coroutines[0] so their memory usage is going to be much lower. They come with a different set of tradeoffs but overall their cost is going to be significantly cheaper because bytecode is JIT/AOT compiled to native, the GC has precise tracking of object liveness and because .NET does not perform BEAM-style preemptive userspace scheduling.

Instead, .NET employs work-stealing threadpool with hill-climbing thread count scaling to achieve optimal throughput. This way, when the workers cannot advance all submitted work items in time, additional threads are injected, which are then preempted by kernel thread scheduler. This means that even if other workers are busy, the work items will not wait in the queues indefinitely. This is a pathological case and usually the thread count varies between 1-2x physical core count.

This has a downside of achieving potentially worse scheduling fairness, and independent tasks allocating can and do affect each other w.r.t. GC pause impact. I believe this to be non-issue because this is more than compensated for by spending <10x CPU time vs BEAM on computing the same result, and significantly less memory (I don't have hard numbers but .NET is quite well behaved in terms of allocation traffic) too. At the end of the day, Task<T> is designed for much higher granularity of concurrency and parallelism so it would be quite unusable if it had greater cost.

If you're curious, I made an un-scientific and likely incorrect but maybe interesting comparison some time ago (it's in Ukrainian but the table is readable enough I hope):

https://gist.github.com/neon-sunset/8fcc31d6853ebcde3b45dc7a...

This calculates the CPU time and max MEM RSS usage required to spawn 1M tasks/coroutines/processes/futures that sleep for 5s and await their completion.

[0]: This might stop being true in a pure sense of the word in .NET 10 because the task handling is going to be completely changed by replacing state machines generated by a language that targets .NET with specially annotated methods, for which the runtime itself is going to implicitly emit state machines instead, allowing to pay the cost only at "true" suspend points. Reference: https://github.com/dotnet/runtimelab/blob/feature/async2-exp...
I love LLMs. I love the doom and gloom. Why? It’s a giant filter.

Because all the clueless people in the room see it as doom to software engineers, because they have no real skills, and can’t think for themselves - and because of this they don’t understand the pros/cons/trade-offs of the tool that is an LLM. And so, they give up on their career or study something else, and no longer crowd the market. Win for me.

These are the same people that would have feared: the mouse when it was released, GUIs when they became the norm, the internet, low-code, no-code, WYSIWYG editors, and crypto.

LLMs are massively overhyped, someone who knows their stuff that has used them daily would know that. And they would understand how to wield them.

I’m not worried about my career at all. In fact, I’m doubling down hard on software. Tripling down even.

I’m learning as broad as I can, and as deep as I can where I care to.

If you know computer science fundamentals, computer architecture, and system design you are untouchable.

Go touch grass!
> I don’t know anyone that wants a partially functioning stovetop

Maybe some repair shop wants to buy it cheap, to repair, and to sell for profit? Or not buy, but to repair it to you for a fraction of the price of a new stove top?

> Also, the new stovetop is far more energy efficient than the old one with is yet another balancing aspect of replacing old tech.

This is the killer. If new things are better then it may be not economically viable to repair.
Comanche, LHX Attack Chopper, Gunboat and Wolfpack. A handful of military sims meant hundreds of pages of specs to sift through -- best copy protection I ever had to deal with. I probably spent more time reading the manuals than I did playing the games.
Hm... I guess the argument here is something like: we don't build 10,000 F-35s because we can't train 10,000 pilots. But with drones, the pilots are no longer a limiting factor so we can plan to scale drone production beyond what we do airplanes?
I majored in English, but I am now a software engineer.

A few things that have held constant for me:

* Readability over cleverness

* The importance of having an outline (even if you don't stick to it)

* The importance of having something that you can work on. Nothing worse than a blank screen.

* Giving and receiving feedback constructively

* The importance of genre and conventions
I have wondered about that, and I'd guess the thing you (and the sibling comments) pointing out about how GH seems to take an html-fragments approach versus GL opting for the more traditional(?) AJAX one probably does matter a great deal on the end user experience

Regrettably, since GH doesn't develop in the open, it's hard to have an apples-to-apples between the two in order to know if GH has some really, really tuned RoR setup, or it literally is just a matter of "don't be cute" when sprinkling every JS trope known to man upon your web ui and if GL one day cared about their page load times, they, too, could be quick without needing a RoR nor RVM upgrade
Zoom screen sharing just crashes randomly on literally every setup I've tried, including Windows.

Just stick to the web version, it's way more stable
I ebb and flow with burnout, as I'm sure most founders do. I also have kids lol. Happy to chat about it via email or w/e.
Updated. Do you think the current one is ok?
Nobody can hold you to account for what you said in the past if you wipe the evidence.
The problem is, I expect reminders to be absolutely reliable. In some cases they could be a matter of getting fired or not, or even life and death, like my weekly "check the lint trap" filter.

I'm online a lot, but not 100% of the time. It might work for some things, but I'm not a fan of using different tools for different important things when one general tool will do, there's more to go wrong that way.
Yes, I have read and found similar articles to what you've posted!

It is an ongoing exploration for us to find the best way to store/consume reactive state data within our client sites/apps. So far, MobX has given us a lot of leeway since we can create the data store we want for our data.

Going forward, I foresee us switching to something closer to WatermelonDB or maybe even just SQLite with a thin wrapper in React to create observability. I'm not 100% sure where it's going to go, but I agree with you that flexible state management for large platforms evolves fast and the difficulty of creating fast look-ups rapidly approaches "reinventing the DB" client-side.

I've had to build similar on top of SQLite for various other mobile/desktop apps, the problem hasn't really changed, the only difference is we're now using React + JS instead of C++, C#, or Java.

All roads so far have led to SQLite though.
But these things are also gems in Rails the same way they are crates in Rust, no?
The translation by Augusto de Campos? That one is amazing!!!
Rust is nowhere near displacing C++.

There's typically a "exhaustion" phase with mono-memetism/theories where everyone gets sick and tired of the "one and only way" and it becomes fashionable to try out new things (eg. Xtianity in Europe). We're not at this point where the olds can be toppled.
Russian troops are definitely poorly prepared. Likely Saddam's troops were in a better shape in 1991, when the same tanks clashed in Kuwait: Abramses and Chieftains vs T-72s and T-80s. Then the Western tanks showed an overwhelming advantage. Now about a quarter of Abrams tanks in Ukraine were rendered inoperable, some of them plainly destroyed. Tanks did become more vulnerable to anti-tank weapons.
Why not just add telemetry to see when requests are retried?
Wow, it looks almost exactly like LHX. You weren't kidding. But can I watch from the viewpoint of my TOW missile camera, I wonder...

Thanks for the link.
All of those have always been the case though, it only wasn't if it wasn't. It's not like nearly everyone was inclined to jump on Vent and raid, that's always been relatively few. Only more recently have there been some systems that make lower tier content less requiring of vocal comms, but for anything demanding it's still pretty typical.
An air-to-air missile is essentially a single-use drone

Yeah.

And barring some big advance, an air-to-air missile can't be any smaller than it is currently. It needs to carry enough explosive to damage the target aircraft, and it needs enough fuel to travel at supersonic speeds for a long enough distance to actually intercept the target.
If the backup generators had been put on a simple platform, the plants would never have melted down.
> That's not quite a fair comparison. The issue isn't Google v Apple--it's Google/Apple creating vertically integrated software platforms where they have a monopoly on App Stores.

That's the exact reasoning I'm calling tragicomic: They are competitors, neither of them have a monopoly on app stores. If you say that two competitors have a monopoly, then you can say that for example all car manufacturers are in a monopoly on making cars. Sure, then the word monopoly doesn't mean anything, and we have simply removed a word from the vocabulary and made everybody dumber.

Your points and comparisons are valid, but they haven't anything to do with a monopoly.
Visual Studio Code is the proprietary version (under the Microsoft Traditional License) of the open-source Code - OSS repository (licensed under MIT). Most of the code is open source, except for a small portion that includes elements such as code used for or providing access to services we run in our data centers (e.g., access to the Visual Studio Marketplace).

Summarized from the following article: https://github.com/microsoft/vscode/wiki/Differences-between...

If your whole business depends on leeching off of someone else’s servers, you should probably be contributing to those servers in some way.
colorful cellular #3
There could be secondary factors. If you're physically hard on your devices, you might be scuffing up screens and permanently smooshing USB sockets with a couple years of hard use. Yes, they might be repairable, but the breakeven math is getting pretty close.

Replacing every 2-3 years also means replacing the battery every 2-3 years, which you were likely going to want to do eventually anyway.

TBH, I don't get the flagship phone thing at all. When my employer was paying, I got some of them-- a Lumia 1020, a LG V10, and a Samsung GSII-- and I didn't really use any of the performance. The phone that was the biggest upgrade for me was a Umidigi F1, because it really had two-day battery life for the first time.
Yeah, everyone with different opinions from you is an evil cartoon character. You're the reasonable and intelligent one.
FWIW, the US communication systems are designed to work in insanely degraded EM environments, they push the bounds of information theory. Bandwidth won’t be great but they will work. The other side of this is that any system that can degrade the environment to that extent is painting a giant target on itself, and the US has purpose-built “seek and destroy” platforms for anything that is aggressively limiting available bandwidth.

A lot of US systems are designed to be functional with bandwidth that is significantly less than an old dial-up modem. In the average case that doesn’t happen but it is an explicit design target to enable operation in severely compromised environments.
They were, in fact, banned from the platform. Nobody was weird, intolerant, or toxic. It is not their right to ignore anyone.
Sorry for dumb question, but does rust have an LTS release? Seems like it’s a lot of nightly builds still
Attack helicopters might still have a limited role in some theaters. But the Marine Corps seems to realigning to fight China in the Western Pacific where, regardless of survivability, regular attack helicopters lack the range and speed necessary to be relevant. They might also face a threat from manned fighters which are potentially very dangerous to helicopters, even those flying evasively at low altitude. Thus the shift in force structure away from attack helicopters and towards the F-35B.

I'm not trying to argue with you and I appreciate you weighing in with firsthand expertise. It's just that current USMC leadership seems to be focusing on different priorities.
Great historical context, ty.

You're right that you may only find a counter to the latest tech once you've lost the war, or you may never find it and you'll only see the victors over you displaced by someone who does find a counter and now rules over you instead of your first enemy.
Banning anyone for any reason from any service or platform is opposition to free expression, end of.
Honest small talk can reveal similar biases without resorting to a too clever by half ruse.

Unfortunately, I have a problem where I love jerks, so we'd probably be good friends.
No one who works on it is bigoted, so that would be nonsensical.