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.

"super" is also a Latin word that's valid French.

> Au-dessus de, exprimant une supériorité dans la qualité

https://www.larousse.fr/dictionnaires/francais/super-/75409

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.

The kernel essentially flags the power source through udev, and the rule triggers the script. That can be done programmatically instead of a script as well. libudev is there for that: https://www.freedesktop.org/software/systemd/man/latest/libu...

https://wiki.archlinux.org/title/Udev (userland /dev is what udev does)

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.

https://gist.github.com/andrew/2f81952f4867d1b200bb

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.

Crazy times.

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.

No need for a human to feed the dog, a robot will refill the dog feeder.

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.

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.)

TOML gets pretty close to a `.ini` file as a standardized parser, taking the original format idea a little bit further.

https://toml.io/en/

It's a bit like any early industry, from cars to airplanes to trains. Earlier models were made by a select few people, and there was several versions until today where GM and Ford have thousands of people involved in designing a single car iteration.

I was on the DVLUP project where Nokia and Microsoft attempted to inject energy into windows phone app development. We could see the tension between the two companies as we were a 3rd party contracted by Nokia to build the platform. The Nokia exec we were in contact with was fantastic, and really tried to make Windows Phone a success. Unfortunately the Nokia IT teams we worked with were not happy and essentially tried to sabotage through inactions (we just needed OAuth / SSO to link accounts and track app installs, it took over 3 months of email chains within Nokia).

Front-ends are essentially free distributed computing resources while the backends need to be paid for.

Could you elaborate on this? Both ARM and RISC-V have standardized their hardware feature and different target versions.

Is it more on the iterative angle given X86-64 now moves very slowly?

Think of an old brick building with several stories and a window per floor vs a new steel + concrete building with windows spanning multiple floors.

The "older" builder like the converted one in the parent post has small windows, allowing easy subdivisions. Newer buildings have windows spanning multiple floors and need to be retrofitted and on a skyscraper that comes at a huge cost.

The bigger ticket item is the plumbing and ventilation, and to some extent the electrical. Ventilation is needed around the cooking area and washrooms, adding that to a building not purposed for this is challenging (where does the "contaminated" air go out?).

It's often cheaper to bomb down the building and start over than doing a conversion on a new highrise. You'll see this often where they gut the entire structure and floors, keep a few walls/supporting structure, and build new.

Some places have limited buildable land and Airbnb was taking over a lot of long term rentals.

Example of how this affects larger towns: https://montreal.ctvnews.ca/montreal-tenant-receives-evictio...

I live in a resort town where we implemented strict rental licenses as otherwise the whole town would be on Airbnb, with nowhere for locals to live. There's no more land to build on within 50km. We're seeing a lot of housing be torn down and rebuilt as 4 unit townhomes on the same land.

The town is now attempting to balance between vacation homes and long term rentals, with fines for unlicensed Airbnbs.

That's a problem. No one is saying it isn't.

The role of Airbnb cannot be ignored; it is negatively affecting housing availability as landlords can make much more profits on short-term rentals than long-term ones.

On the building side, we've made it much more difficult to build low/mid rise apartments buildings.

General accessibility requirements alone make it impractical to build anything less than 5 floors with a large land footprint (~20 units per floor). You pretty much need an elevator and other accessibility systems, which makes construction and maintenance of low to mid rises prohibitive. Older constructions are filled with grandfathered clauses allowing them to skip over accessibility requirements.

This is why you only see requests to build ~20+ floor buildings, which people disagree to be added in their neighbourhood.

ex: https://www.ontario.ca/page/accessibility-ontarios-building-...

> Barrier-free floor access is also required for residential and office buildings over:

> 3 storeys high

> 600 square metres in building area