Hacker Newsnew | past | comments | ask | show | jobs | submit | scoopr's commentslogin

There is a bbc podcast[0] about evilcorp

[0] https://www.bbc.co.uk/programmes/w3ct89y8


The podcast includes the author of that blog post and is also linked in the article.

> Both Baldwin and I were interviewed at length for a new weekly six-part podcast by the BBC that delves deep into the history of Evil Corp.


> Every once in a while I pull up some Wikipedia article with idle curiosity of "If I were transported back in time, could I usefully help this get invented?"

This reminds me of the book “How to invent everything” by Ryan North, to kind of see the fast-path for many inventions :)


Then there is the proposal to add standard `defer` to C2y[0]

[0] https://thephd.dev/c2y-the-defer-technical-specification-its...


It's been implemented in GCC(in review)[1], onramp[2] and my own slimcc[3]!

[1] https://patchwork.ozlabs.org/project/gcc/list/?series=470822

[2] https://github.com/ludocode/onramp

[3] https://github.com/fuhsnn/slimcc


A good example of adding stuff to the standard with community feedback from a preview implementation.


Jen's macro that this was based on was an implementation of his own proposal (N3434) for `defer`, which was one of a few preceding what finally became TS25755! So, yes, C2y is lined up to have "defer: the feature", but until then, we can explore "defer: the macro" (at least on GCC builds, as formulated).


Heh, little prince tries gig work ;)


100% had the same little prince connection the moment it loaded. Quite pretty indeed.


Heh, in Finnish it is often called “miuku mauku”, almost like “meow meow”, or perhaps “meowdy meowdi”. Didn’t see any other cat-themed nick names.


I've occasionally pondered, how feasible would it be to write a APFS implementation just from the specs[0] alone. Is it harder or easier to create the implementation when you have a provided layout and mechanism how it works. Would it be easy to keep compatibility, and would it be a dead-end design for extensions that you'd like?

[0] https://developer.apple.com/support/downloads/Apple-File-Sys...


Can tell you first hand that while the specs are useful, they do not cover APFS as it is deployed by Apple today.


While technically true, f.ex. Finland has stopped all mail shipments[0]. I guess the airlines were not set up to dealing with the hassle of making sure all the shipments are “allowed”. Or maybe just lazy, dunno really.

[0] https://www.posti.fi/en/latest-news-at-posti/%20/news/trump-...



Probably mentioned on every teletext related submission, but the Finland's public broadcaster YLE still has an avid teletext userbase, if not through a proper TV, then through the website [0] (and there are mobile apps for that too).

Some of the news listings are perfect, given confined space, but no need to be click-baity. See, f.ex. the news-in-english page [1]

[0] https://yle.fi/aihe/tekstitv

[1] https://yle.fi/aihe/tekstitv?P=191


The original edit.com, from around dos 6.22 (and later 7.0, ie. win95) was my first IDE. Well, I started with qbasic, so I was fairly familiar with it as it was similar (or same?), but when I started learning C/C++ with djgpp, I just continued using edit.com.

My "project file" was `e.bat` with `edit file1.cpp file2.cpp file3.cpp`, as it was one of the few editors that I knew that had a decent multi file support with easy switching (alt-1,2,3 ..). I still continue remapping editor keybindings to switch to files with alt/cmd-1,2,3,.. and try to have my "active set" as few of the first files in the editor

It wasn't a great code editor, as it didn't have syntax highlighting, and the indent behaviour wasn't super great (which is why in my early career had my indent was two spaces, as that was easy enough to do by hand, and wasn't too much like tab). But I felt very immediate with the code anyway.

I knew that many others used editors like `qedit`, but somehow they never clicked with me. The unixy editors didn't feel right in dos either.

Quickly trying this, it doesn't seem to switch buffers with the same keybindings, even if it does seem to support multiple buffers.


You should raise that as an issue. If things like that get in early enough, they get heard.

And it wasn't just similar. It was literally the same. EDIT.COM simply started QBASIC up with a special flag. One could just run QBASIC with the flag. As I said at https://news.ycombinator.com/item?id=44037509 , I actually did, just for kicks.


It may not have had syntax highlighting, but it did have syntax capitalization (for lack of a better term?). If you typed a line in all lowercase, after hitting enter it would automatically uppercase the reserved words. It wasn't much, but it helped


edit was a godsend after the `copy con` days


I remember using edlin a lot in my early computing days. It was murder to learn but once you knew how to wield it, it was excellent. I don’t know why I was forced to learn that but I needed it for something and stuck to it the entire time I used DOS for anything. And people were in awe when you used it while they watched. “What the hell was that!?”


Could be perhaps worth the trouble to try dev-drive/ReFS? [0]

[0] https://learn.microsoft.com/en-us/windows/dev-drive/


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: