zedr
It's being written entirely in Python: Kivy for the desktop and mobile game UI, and aiohttp for the server.
I've written very detailed specification documents for every technical and game-design aspect of the game, and I've implemented the core game engine myself. I'm letting an agent do the rest, incrementally and under supervision, tweaking the specs as we go along. So far, a very pleasant experience.
My goal is to reach beta by the end of the year, and publish the game on Steam by mid-2027.
1. The mouse is a hardware sprite and its movement stays responsive and smooth even under heavy load and even when the OS freezes
2. A screen can be divided into multiple resolutions, e.g. you can have a half a screen in high res and half in low res and with double the amount of simultaneous colors (or even HAM mode)
3. It can genlock natively, i.e. match its screen refresh rate with an inbound video signal, making it popular with broadcasting studios up to the late Nineties
Fabien seems to be unaware of this, by the way.
This is also why the game play is so bland. The number of 3d objects and their complexity was severely constrained and did not allow for varied or more sophisticated game elements.
Silpheed was amazing back in the day. It was one of the first titles that really showcased what CD drives could add to games in terms of cinematic experience. The live orchestral music gave it an epic feel and the mecha-design of the SA-77 is beautiful and modern even by today's standards.
EciAdsl, story of a driver unlike any other (2004)
My take on it:
class Stuff:
def __init__(self):
self._list = [1, 2, 3, 4]
@property
def each(self):
for el in self._list:
yield el
for item in Stuff().each:
print(item)
It's even less verbose than the Ruby equivalent in the original article, thanks to the indentation-defined blocks.My favourite brutalist building is in Belgrade: the Western City Gate https://en.wikipedia.org/wiki/Western_City_Gate
Dieter Rams' design principles applied to software engineering
Strictly speaking, that's not what REST considers "easily discoverable data". That endpoint would need to have been discovered by navigating the resource tree, starting from the root resource.
Roy Fielding (author of the original REST dissertation): "A REST API must not define fixed resource names or hierarchies (an obvious coupling of client and server). (...) Instead, allow servers to instruct clients on how to construct appropriate URIs, such as is done in HTML forms and URI templates, by defining those instructions within media types and link relations. [Failure here implies that clients are assuming a resource structure due to out-of band information, such as a domain-specific standard, which is the data-oriented equivalent to RPC’s functional coupling].
A REST API should be entered with no prior knowledge beyond the initial URI (bookmark) and set of standardized media types that are appropriate for the intended audience (i.e., expected to be understood by any client that might use the API). "[1]
1. https://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypert...
Show HN: Dieter Rams' principles of good design applied to software engineering
Homeopathy
Write your app in pure Python. Deploy on desktops and mobile devices.
The main disadvantage is that it does not use the native widget toolkit, although there are projects like KivyMD that attempt to replicate the native look and feel by theming the UI.
I also wrote a blog post on how to install it: https://medium.com/@zedr/how-to-send-mail-on-namecheap-share...
Excuse my frankness. That's not a fact. That's unfalsifiable woo-woo.
> “If there is a human moral to be drawn, it is that we must teach our children altruism, for we cannot expect it to be part of their biological nature. ”
Let me quote another favourite author of mine on the same topic:
> "There’s Nature, and she’s going to come out the way She is.", Feynman.