No disrespect for the OP, but this is just the same anti-UI-advancement crap we hear from Linux people all the time, since the 1990's. I still remember having to idiots drone on on how "this gui thing is just a fad, real men using 80 char terminals". Despite what the OP is trying to convey, there's a big, big ocean between banging text on VIM like a caveman, or waggling your WiiMote like a useless idiot. A mouse, for starters, would help very much. I would ask for touch support, but since for the fanatics, even using a mouse is heresy tantamount to using closed-source!

Mad props for maintaining MFC, the most OS respectful way of making software for Windows up until the late 2000's. To be honest, I don't miss the clustefudge of files and declarations for UI construction, but when it worked, oh boy did it work!

The cheapest solution while maintaining low power is probably an Nordic nr51822. You can get them dirt cheap, have BLE included and an ARM M-0. Combine that with an ST-Link and Visual Micro and you're ready to get some firmware working on a tiny chip.

If you have dealt with Unix fanboys, you'll now doubt have encountered the stupid "which hacky character shall we use for white space: spaces or tabs?". The correct answer is "whatever the team is using, I format it to that before committing". As for consistency, I only really am a stickler with fucking braces. I've seen too many recurrent bugs because a programmer is cute and makes a braceless if. Then the next one comes in, adds one more call and doesn't realise the braces are gone. Ooops, billion dollar bug introduced. Nasty and no need.

Quote:

I have been brainwashed to NEVER do: if (a) b;

Good for you, you are ready to avoid a billion dollar bug because "I don't need braces or consistent rules".

Quote:

hey wouldn't mind generating segment:offset addresses that past the megabyte barrier, because it will roll over and map into the address space of the zeroth+ segment

Absolutely disgusting, this is the recipe CREATE legacy shit right from the start. I can't even imagine the hacks Microsoft must have had to do keep old Win32 apps working in a modern OS.

Web developers working on a 80 char terminal, trying to be "efficient" and clever: "Less lines means it's faster, right?" - every noob web developer "Who cares about indentation, we save 2 lines here this way!" - Apple before the SSL fiasco.

Thank you, sometimes its good to read some sanity.

Quote:

So here we are now writing software whose responsiveness would make the 90's VB guys laugh all

Oh god, we now have web-browser based text editors! Type key, wait 300 ms (on a 2019 i9 with 64 GB RAM) and then the text shows on screen. I hate it.

Welcome to 2019. Text editors are a browser now. Messaging apps are browser now. IDEs are a browser now. Every browser is Chrome. Chrome will take 1-2GB for every instance. F**k you if you want a pleasurable experience, go buy the new MacBook i9 with 64 GB of RAM.

If you plan to run multiple OSes, you're advised to pack a lot of RAM, whichever your host OS is. Because the guest OS (Chrome) will not be appeased by single digits gigs of RAM.

Buy a pair of 2$ micro controllers off ebay. Buy a pair of radio ICs (doesn't really matter much, as long as its not BLE or WiFi). Configure radio IC. Send a packet. Be amazed. Spend next 6 months working on a low level network for micros. Worked for me :-\ Sincerely, an EE who skipped all tele-communications classes because they sucked.

The topic is on Swift language, not a particular IDE. And for the record, programmers at Apple are old-school idiots who think syntactic sparseness is compatible with security code worked by other 5000 people.

Quote:

IMHO it's requiring coders do what's basically IDE's job.

Ding ding, we have a winner. Did not expect this from Apple.

Yes, give researchers better tools, I've seen the impact of researchers using Python instead of Octave/Matlab: instead of hacking primitive operations and memory, they can focus on the data itself and logic. Just don't let computer researchers around a compiler, god knows what they'll make of it next (Remember C++ evolution....).

Goodness. You've made about 5 people stare in awe at me, when I said "1996" . Most guesses were around 1981-1986. Pointer arithmetic and stuff like that is why you can't let scientists develop software. I mean, someone had to invent the bloody things, but leave the actual programming to Computer Science.

Chris Maunder wrote:

Firstly, If a keyboard and mouse is the pinnacle of human-computer interaction then I'm quitting this industry now. The keyboard and mouse are a stop-gap measure - a long term stop-gap measure - but one that needs to be replaced.

Let's hope you never have to deal with Linux people: they think the pinnacle of human-computer interaction is typing on a keyboard. No mouse. No touch. No voice. No scroll. No click. No pen. Just tap.

"register" and "pirate" were but concepts at that age. Besides, were I was from, piracy was the norm. Hell, my cousins had games life "Flashback", which required the photocopied manual as an anti-piracy feature.

I was 12, give me a break :P

Kinda makes me want to make a PSP-like image editor on UWP. Oh god, I remembered just now, I registered my (Pirate!) copy of PSP with Jasc. Then, the Jasc spam came in snail mail. The 90's were weird.

Quote:

Paintshop Pro 10

OMG, the last image editor I liked using. Photoshop's better nowadays, but the for the most part, the UI was legacy shit. Not PSP, use it since version 2.0 I believe :D