What you are looking at is corporate environments; the studios of the past (Ex: Westwood and Blizzard) had a small headcounts, and people were direct decision makers.
> StarCraft was originally envisioned as a game with modest goals that could fit into a one-year development cycle so that it could be released for Christmas, 1996
> Warcraft II had only six core programmers and two support programmers; that was too few for the larger scope of StarCraft,
No boardrooms of PMs, and Directors, and VPs, and execs, chiming in every decision, leading to fast turnarounds.
I'm pretty sure they know, and that's what makes it funny. There's an entire genre of internet humor based on using incorrect (because of homophone/homograph words) english-to-french translation. For example saying "vérifie les buches" for "check the logs".
2) The use of the TLD .gouv.fr instead of .gov.fr, even though "gov" is a recognizable contraction of the intended French word "gouvernement".
(No, it's not a valid defense that "'gov' would be pronounced differently from 'gouv'": the English TLD .com is a contraction of "commercial", even though the "com" in "dot-com" is pronounced differently from the "com" in "commercial".)
Probably because of their proximity with the USA, the french-speaking community in Québec is far more attached to using French than actual French people.
That's why in France we use "Stop" and not "Arrêt".
On the other hand, ".gouv.fr" is something used in France.
gouv[ernement] is completely different than go[u]v[ernement]
Not only because of its pronunciation, but also because it's not a simple shortening of the original word.
We never use "aso" to talk about an "association", even though it would shorten it even more, because it just doesn't make sense.
You can remove the ending of a word, creating a kind of "prefix", bug it you remove multiple part of a word it just become something different.
>On the other hand, ".gouv.fr" is something used in France. gouv[ernement] is completely different than go[u]v[ernement]
How are they different? Contractions and abbreviations drop letters. That's the point. .gov would have been perfectly fine and matched other countries. It's a clear example of being different for the sake of it.
I might have picked "desu" as the keyword, a shorter phonetic respelling of dessus. Since the super keyword is often repeated in Rust, this would lead to code like `utilisons desu::desu::desu::a()`, for some added Japanese flavor.
This is pretty much what this solution does, but through udev.
Systemd, D-Bus, and udev can be used separately or together to make this easier to listen in userland, it will just be dependent on your distribution or setup.
If you mean "some apps have ads in them," that is true. What I mean is the OS doesn't have ads, unlike Google and Amazon's competing products... And unfortunately even Roku now.
You are free to never open apps that have ads in them on the Apple TV.
(If you mean: installed apps are allowed to show content previews when you hover on them in the UI — I think that's pretty different from an ad, and it's a feature I personally like, since it means I can easily resume a show I was previously watching without even having to open the app-specific UI. That's quite different from my perspective than showing ads for services and apps that I've never used, that I can't remove.)
OpenCV and other onboard computer softwares can be trained to recognize shapes, 10+ years ago there was a demo of a NodeCopter controlled small drone following red flags.
Stick the GPS coord, fly there, and once in a geofence look for a shape to crash into doesn't seem impossible given what was possible 10 years ago.
Hell, 30 years ago I was working for the MOD (they sponsored my PhD and turned it into an RA) in the UK creating context-aware neural network inference engines for FLIR (Forward-looking infra-red) data. We had all sorts of "fun" stuff running on a Meiko computing surface, with parallelised network training and implementations, temporal and spatial averaging, and relaxation labelling all thrown into the mix to aid the recognition engine, done with a voting system of various architectures sharing to a "blackboard" where information could be posted to and read from. Visualisation was all on high-end (for the time) Silicon Graphics workstations.
The context (together with the features extracted) was the killer (forgive the pun) feature though - everything else reduced noise, but context increased signal.
My gast remains flabbered that the sort of thing I was working on back then hasn't become commonplace in the interim. The computing power available today, compared to then, and the accuracy we had (I know for a fact at least one of the designs was made into real hardware, it was called RH7, and "RH" stood for "Red Herring" - oh how we laughed) ... It beggars belief that it was just left to digitally rot.
There is often quite heavy GPS jamming or spoofing. Also in some of the published videos I think you can see a "no GPS lock" status message - but maybe they just did not bother with GPS if all the drones were manually piloted anyway.
Yes, I assumed they didn't need GPS because they knew exactly where the trucks that were the launch sites were to be placed and they knew approximately their targets would be sitting on a certain section of airport tarmac. The pilots would have had a detailed satellite photo map of their entire route until visual target ID was possible. While GPS was probably partially jammed, that deep in Russia I doubt it would have been as severe as near the front lines. Plus there wouldn't have been heavy jamming of the local drone control frequencies because they weren't expecting a drone attack there.
To me the more interesting question is how they managed sending the real-time video feeds and control data. Since the trucks were mobile, I assume it had to be via a bunch of mobile phones signed up to Russian service providers since Starlink doesn't work inside Russia. To reduce latency, I wonder if the phones were connecting to a covert site in Russia which had a high-bandwidth wired link, maybe a front company established for the operation with servers and broadband internet connections.
GPS is heavily jammed throughout Russia, and the ArduPilot overlays shown on the videos released directly show there was no GPS lock (might not have been equipped as I'm sure they'd be expecting this).
Given these are static targets, it might be possible to relay precise GPS information from that morning’s satellite data. No real time intelligence required. Just dead reckoning to the target coordinates.
Operation in GNSS-denied areas is already a stock feature on many relatively inexpensive commercial drones. The manufacturers talk about it euphemistically for obvious reasons, but they're designing drones specifically for the Ukraine war. There's a huge amount of engineering effort going into building drones that can remain operational in an extremely hostile RF environment.
Compensating for wind drift is a fairly straightforward software problem when you've got a fast processor, a bunch of high-resolution cameras and a laser rangefinder.
If you have a downward facing camera you can track your movement like an optical mouse by just watching the terrain. Error will creep in, but you only need to fly a few kilometers till you find something that looks like a strategic bomber.
The big difference is they can now run this on the copter instead of being remotely controlled; a 100$ raspberry pi has enough processing power for this, and so does several other off-the-shelf mini computers powered by lithium batteries.
Gnome2 was a good functional desktop, sure it was copying the 2000s with windows 98/2000 style, but it worked. Hell, even OpenStep is more functional than Gnome3 as a daily computer interface.
Gnome3 targeted a weird mix of incompatible devices, like a windows 8 interface, and kinda failed as a design given the devices it optimized for never took over the market. There's not that many tablets running Gnome or touchscreen laptops anymore.
It's almost like Android took the design team by complete surprise, while they tried to make desktops a tablet experience, but failed at doing both.
> Gnome3 targeted a weird mix of incompatible devices, like a windows 8 interface, and kinda failed as a design given the devices it optimized for never took over the market.
I'm not sure about that. Convertible laptops are quite popular as a product category, and GNOME 3 works great on those. Besides, MATE and Xfce are still around if you prefer a traditional desktop interface.
Agreed. I gave gnome a pass for years because, well it’s largely designed for touchscreen devices right?
Fast forward to 2024 I get a Linux tablet with gnome installed (phosh) and guess what? Not a single gnome video player exists that works well with the touchscreen, and many of the apps only work by keyboard!!
We lost so much in the transition, and they didn’t even bother to nail the supposed new use case. Gnome in itself is a complete failure, so far at least. Cinnamon and Mate are decent but suffer from GTK deterioration. Phosh seems to work well enough.
I like kde these days and have it on a machine, but every time I open the context menu on konsole I get upset because there are a hundred options in there. I want a simple menu.
Nice, I still want to dive into Niri or PaperWM (Niri is inspired by PaperWM but more minimal, needs Wayland and written in Rust where PaperWM is a WM on top of Gnome).
I hear good things about COSMIC as well. But I'm too busy being productive at the moment to mess up my well working NixOS/Vanilla-Gnome based laptop :)
This becomes quickly apparent in a smaller company or if you have a manager that knows what they are doing.
You'll get hired, if you pass the technical interviews, but if you cannot contribute at the level they hired you, you'll be exited and that will be suspicious for your next application.
> This becomes quickly apparent in a smaller company or if you have a manager that knows what they are doing
Sounds like an unlikely problem and by then you can pull a reverse end run around your manager to their manager who doesn't know what they are doing and will believe anything the guy who worked at google says.
yup! FreeBSD jails are essentially what OP wants with chroot++.
I was pretty puzzled when Docker and LXC came around as this whole new thing believed to have "never been done before"; FreeBSD had supported a very similar concept for years before security groups were added in Linux.
Jails and ezjail were stellar to make mini no-overhead containers when running various services on a server. Being able to archive them and expand them on a new machine was also pretty cool (as long as the BSD version was the same.)
this whole new thing believed to have "never been done before";
Nobody with knowledge of sandboxing believed this, Virtuozzo and later OpenVZ had been on Linux for a long time after all. Virtuozzo was even from a similar time frame as FreeBSD jails (2000-ish).
The key innovation of Docker was to provide a standardized way to build, distribute, and run container images.
Virsh had worked for a long time before docker came around, but yeah… you essentially had to build your own Docker-like infrastructure that only you were using
The story of Starcraft 1 is quite interesting as the devs copied the Warcraft 2 code and began changing it quickly[1](https://www.codeofhonor.com/blog/tough-times-on-the-road-to-...).
> StarCraft was originally envisioned as a game with modest goals that could fit into a one-year development cycle so that it could be released for Christmas, 1996 > Warcraft II had only six core programmers and two support programmers; that was too few for the larger scope of StarCraft,
No boardrooms of PMs, and Directors, and VPs, and execs, chiming in every decision, leading to fast turnarounds.