23,650 karma · joined October 15, 2013
They can simply throttle access for everyone to a push/merge frequency which was normal for human-maintained projects.
They should look at how MMOs battle cheating/botting and apply similar countermeasures (it's actually quite absurd that MMOs which are actively attacked every minute have a better uptimes than Github, and on Github the problems are even self-inflicted, not caused by external attacks).
But of course throttling bots to human-level push/merge frequency wouldn't be compatible with the Github leadership's 'AI bullishness'.
Aren't those two things contradicting each other? ;)
I think macOS getting more sluggish in each release (which is objectively true) is just plain old bad software engineering and prioritising the wrong things. E.g. it's just Apple's version of "What Andy giveth, Bill taketh away.".
The Wikipedia article has a nice map what countries use which convention (search for "Current Usage"):
There's a 10 minute timer on HN to avoid discussions becoming too heated (at least AFAIK that's the reason).
> You are essentially asking them to adopt an open-source model. That can mean giving up control over its intellectual property and potentially exposing proprietary technology to competitors, especially when some products are valuable precisely because of the software that runs on them.
...and nothing wrong with that. The right-to-repair is mainly aimed at discontinued products anyway, at that point the "IP" is so old it doesn't require protection (and to be honest, the whole concept of long term "intellectual property" is bullshit anyway, just as long-term "copyright" - about 3 to 5 years is a reasonable time frame for 'exploiting' a novel idea, after that it should be free for all - at that time your competitors will have figured it out anyway).
In the 80s it was entirely normal to get parts lists, schematics and ROM listings when buying a computer for instance (and I guess other electronic devices too), there is absolutely no reason why access to the same information should be restricted today.
And in a way, those old 8-bit home computers also worked like a single integrated 'super-chip', because the whole system was driven by a single clock and entirely 'hard realtime', while modern computers are much more asynchronous (and I guess this asynchronous design is what enabled most performance improvements that go beyond pure transistor count scaling).
The ISA is quite messy because of the backward compatibility requirement with the Intel 8080 (e.g. the Z80 had to fill undocumented gaps in the 8080 opcode encoding map with new instructions, four of which were prefix instructions to unlock additional instruction 'subsets' (DD/FD for replacing instructions involving the HL register pair with indexed addressing modes via the IX/IY registers, and ED/CB prefixes for adding two entirely new opcode blocks).
If the Zilog engineers would have been free to design their own ISA I'm sure they would have been able to come up with a much more elegant design.
Also the Z80 had more than twice as many transistors as the 6502 (8500 for the Z80 vs 3500 for 6502).
I still prefer programming the Z80 over the 6502 though :)
This I don't understand? Zig structs are pretty much the same as in any other language, except that the declaration can be more flexible by building the struct type via comptime code (e.g. how Zig does generics) - and Zig groups structs and namespaces under the same keyword (which hardly matters in practice though).
> @SpecialThing
...not any weirder than `__builtin` keywords in Clang or GCC and at least in Zig it's obvious that anything starting with a `@` is a builtin, while in Clang/GCC the `__` is not explicitly reserved for builtins. ObjC also uses a leading `@` to separate ObjC keywords from regular C keywords. Agreed that the @-noise can get a bit excessive in Zig though (mainly because implicit casting is heavily restricted, at least compared to C).
> Multiline strings are also a weird addition
AFAIK the 'weird' multiline syntax is for keeping the parser simple and fast. Multi-line-strings themselves are a good feature to have though.
In general, if Zig code starts to look too 'noisy', that's usually a sign that the code should be simplified.
I definitely don't agree with all design decisions in Zig, but the syntax is mostly fine (my main critique points are that Zig often tries to lean too much into 'design purity' than 'programmer convenience' and that parts of the stdlib are too 'object oriented'.
But that's just my opinion.
Such questions usually come down to "how familiar am I with this programming language", and anything that doesn't look like your pet language looks ugly. Except Rust and C++ of course, those are objectively ugly ;P
https://store.steampowered.com/app/1489630/Carrier_Command_2...
And within a mission you always need to maintain 'tactical awareness', always have an escape route in mind, scout ahead for guard routes and schedules, hack doors and cameras, select the best approach to tackle a specific type of guard or robot. And then of course no mission goes as planned, your team gets pinned down and you need to fight your way out or find a place to hide until the alarm level cools down.
Also depending on the approach you choose for a specific mission you may need to change your team's equipment and cyberware before entering the mission area, or maybe you decide that it's better to first raid the military barracks of the district, hoping to get some new weapon and cyberware blueprints. Or you spend some downtime looking for scientists to hijack (which increase research rate for blueprints), or look for new random people in the streets with better attributes for cloning. Or running low on money maybe it's better to first rob the district bank. Each new district is harder than the last, and during the entire game you're essentially preparing for the final confrontation with the main baddy.
For a relatively small indie game there's a lot of 'gameplay density', I can understand though that the game may feel repetivite, but especially starting to tackle a new district may quickly feel like routine, but that initial routine only exists as preparation for the two or three main mission areas in the district, and those are the 'meat' of the game.
Especially the Amiga and Atari ST were much bigger in Europe than the US (mainly in Germany and the UK, and for Atari ST also France).
Satellite Reign has been released as a full game, playable from start to finish and it's really excellent (no idea tbh why the Steam reviews are stuck at 'Mixed', kids these days smh...). It takes a bit to get into the 'flow' and discover all the little gameplay details but once you "got it" it's a lot of fun. I usually do a playthrough at least once a year.
Also re Pirates: one of my favourite 'strategy' games on the Amiga. The 2004 remake in 3D is fun but the graphics really haven't aged well and the art style wasn't all that great to start with.
I'd really like to see a modern 2D Pirates remake with a bit more historical details and fewer gimmicks (e.g. no sword fights and QTE dancing please).
XWayland is essentially the missing mid-level "Wayland client library" which fills the feature gaps caused by missing extensions of the underlying Wayland implementation and it provides a common and fully featured GTK/KDE-agnostic window managemnt layer. Until the Wayland project releases a client library 'for the rest of us' with a similar intent, XWayland is still very much needed for applications that don't want to or cannot link against GTK or KDE for various reasons.
Apparently easier and faster parsing. Most modern language have arrived at the `fn bla(arg: ArgType): ResultType` form and I don't think they made that decision for purely aesthetical reasons.
> and it looks a bit underwhelming in general
...only from today's perspective.