Hmm, my first reaction was the same as yours. But I have quite bad eyesight and looking at the "regular 400 at 16px" example on the page reminded me that I definitely sometimes find myself squinting trying to work out whether a character is a parenthesis or a brace (Droid Sans Mono). So I suppose it'd probably be quite helpful to have a brace that's very visually distinct from parenthesis even if it's not particularly pretty on its own.
Squishing it down to <12px I can see that problem, even when compared to other good coding fonts like Jetbrains Mono or a font designed for readability like Atkinson Hyperlegible Mono / Next.
Definitely was too quick with my judgement. Still, it just looks really out of place at bigger font sizes and it makes me wonder if there isn't a more elegant solution out there.
Same guy who made the remaster linked in the article also remastered this one -
https://www.youtube.com/watch?v=MY0bxhbPi3Q - seems he had a retail DVD from Sony with a better original source on it
oh man! every so often for the past decade I've tried to remember "rinkworks". I recognised it immediately from your post. I remember this being one of the first websites I would read as a kid, 20 odd years ago. cheers for the nostalgia buzz!
The trick is to use a metallurgical microscope, which shines the light down through the lens. A regular microscope illuminates from below, which works fine for cells, but not for opaque chips.
Specifically, I use an AmScope ME300TZB-2L-10M microscope, which my friends consider an entry-level microscope, but it works for my needs.
I think the title really undersells it, the video is worth a watch. It's really an impressive effort just to get .NET 3.5 code running on Windows 95, seemingly just to be able to say he could.
HN is usually good for this kind of thing: it looks like NDP is an internal name for dotnet, does anyone here who remembers what it stood for?
I played this for hours last night, I'm going to need to block it :) Set myself a target of 2048 for nostalgic reasons, turns out it takes a long time (for me anyway).
You're right about the dictionary, actually the whole time I kept wondering about how annoying it must have been to choose a dictionary for this game. Even though not accidentally making non-obscure words without noticing is part of the challenge, accidentally making obscure words is annoying!
Maybe I just don't know enough words - but looking through my game log, I was annoyed by "cony", "smit", "huic", "yipe", "nome", "torii", "agon", "mairs", "imido" and "sial", some of which don't display a definition when you click them, but all of which appear in all the scrabble dictionaries referenced on the website you just linked. Meanwhile I was sad to discover vape is so far only in one scrabble dictionary :) And annoyed to discover "oxalic", which is also in all the dictionaries on that site, was not accepted.
I guess there's a spectrum between "advanced scrabble player level vocabulary" and "fun word game", because I imagine (and suspect you have probably had feedback along these lines) _not_ allowing a word which is obscure but still unambiguously used in the modern era would be worse UX overall - the sort that's more likely to make you rage-quit.
I can see why you'd try to get a bit of wordle-esque shareability out of the daily mode even though I like the classic mode more myself. But I think the tutorial popup isn't as comprehensive as it needs to be for someone's first game to be fun. The first time I clicked the link I did an abysmal job at the daily challenge, I think it wasn't obvious that swaps didn't need to be neighbouring like the given example. Something that might be better is to make an interactive tutorial for first-time visitors - come up with a 5x5 board that is quickly solved and demonstrates several strategies and then walk the player through clearing it. I also think the help popup being one click away would be useful.
I would also have liked the help popup to let me know that progress is saved if you close the page, I ended up checking in an incognito window because I had no time to keep playing but wanted to come back and try to reach the target I'd set myself another time!
Anyway - criticism and suggestions aside - well done, it is a fun game and concept!
I think it'd be interesting to connect a high sensitivity / resolution sampling probe directly to the analog output of the drive heads. You could do software-defined signal processing to potentially recover damaged data. These USB-based tools are getting the signal after being amplified in the analog domain and processed by the drive's electronics.
IIRC - he mentioned that someone _else_ had a DEC machine, and actually used it as their dev box. The dev with the DEC box person developed the kernel panic code, aka the blue screen of death - and blue was chosen because that's the default screen colour when the DEC box is turned on. The idea was to reset the colour to the default before printing the kernel panic message.
So while DEC NT is sort of a footnote, it did have this pretty profound influence : )
This is a bit of a game of telephone - NT Alpha shipped after NT 3.1 (i386 & Mips) and the port was done almost entirely by DEC. The blue screen preceded the Alpha and was really based on the color scheme from the firmware on the Mips workstation which Microsoft built internally. And, of course, the legendary SlickEdit, which was one of the original editors available on Win32.
After NT 3.1, Microsoft assumed primary responsibility for NT Alpha, although there were also some great people at DECWest still involved.
source: me, I'm the 'someone _else_' who owned all the Alpha stuff at Microsoft.
reply