|
In my case, most of my posts against Microsoft are mostly in the insider news and more in joke, sacarsm mode than real rants.
At the end of the day I am still using it and will still use it (at least at job)
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
To be honest, I don't understand what the point of that TypeSpec is, because it doesn't generate C# REST API's. 
|
|
|
|
|
Welllllll.... this[^] is what I use on that front.
|
|
|
|
|
https://www.charachorder.com/products/charachorder-one[^]
synopsis : a uniquely shaped keyboard permitting "chords" i.e. simultaneous key strokes also w/ minimum finger movement i.e. each key has four associated characters via joy-stick like motion North South East West. also other product converting conventional keyboard to chording.
|
|
|
|
|
It was hard enough/took long enough for me to learn how to type the first time around. I'd rather not have to repeat it.
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
And my IoT UI/User Experience library here:
https://honeythecodewitch.com/uix
|
|
|
|
|
isnt't this somewhat similar to court stenographer keyboards ?
CI/CD = Continuous Impediment/Continuous Despair
|
|
|
|
|
They each permit chording but the logic differs. Also steno keys have but one value each. Maybe steno keyboards should follow their example and permit joystick like keys so the fingers might never move but merely twitch to the compass points.
|
|
|
|
|
I've always suspected those types of keyboard might be well suited for paragraphs of text, but when it comes to programming languages, where you often have to type brackets, parens, semicolons, etc...how well do they work?
|
|
|
|
|
Chording is not required for all input.
|
|
|
|
|
I remember those keyboards from the early 1980s, but at that time they didn't make any great success. Maybe they will this time.
(My old keybord started failing last week, after 8 years of trouble free operation. Maybe I should consider this alternative for a replacement.)
Religious freedom is the freedom to say that two plus two make five.
|
|
|
|
|
A rectangular, beige keyboard with dark brown fingertip shaped buttons that all fitted under the palm of one hand? I recall something like that too.
The Microwriter[^] - is this what you're thinking of?
|
|
|
|
|
The ones I were thinking of were like two hemispheres, one for each hand, with one button per finger (so you could input 10-bit character codes in a single chord  ). Size was about as if you cut a large orange in two - one for each hand - but I believe that they were black. I never saw them in real life, only photos in ads.
I've got a huge pile of BYTE magazine from the late 1970s and early 1980s, and I was seriously considering flipping through those to see if I could find it there. But the pile is too big; it would take more time than I think it is worth.
Religious freedom is the freedom to say that two plus two make five.
|
|
|
|
|
I don't think I ever saw those.
|
|
|
|
|
Page says "This text was typed at the speed of thought"
I already do that.
And I doubt it is going to make me think faster. So no reason for me to use it.
|
|
|
|
|
|
I've got a manual 6-point Braille typing machine sitting on a shelf in my basement. It really should be placed in the exercise room - it is a great tool for building the strength in your fingers!
Next to it sits a Braille PC printer. The noise level is so high that when we wanted to use it, we had to give all neighbors a warning in advance. It is not functional now; I haven't had a PC with an LPT port for ages. There used to be USB-to-LPT adapters available; I hope they still are if I ever need to put the printer to work again. Currently, I have no need for it.
Religious freedom is the freedom to say that two plus two make five.
|
|
|
|
|
50% of the time, this is a nice feature.
The other 50%, I hate it as I have to clean up the BS it adds. Like
using static System.Runtime.InteropServices.JavaScript.JSType;
using System.Runtime.Intrinsics.X86;
using System.Security.Policy;
using Twilio.TwiML.Voice; Seriously? Where does it think I need those???  And yes, I know I can turn this off, somewhere, but the 50% when I like it, I want it.
|
|
|
|
|
It shouldn't do it when it has to autocomplete the referenced item. For example, if it autocompletes ThreadPool but you didn't type it it shouldn't add the using System.Threading.
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
And my IoT UI/User Experience library here:
https://honeythecodewitch.com/uix
|
|
|
|
|
Maybe that's the problem. I hit Enter expecting what I'm seeing to autocomplete but it does something totally different. I think I often jump the gun on the auto-complete.
|
|
|
|
|
That's exactly what happens to me.
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
And my IoT UI/User Experience library here:
https://honeythecodewitch.com/uix
|
|
|
|
|
What language? 
I just delete them all.
I use the using directive only for aliases and for adding Extension Methods.
|
|
|
|
|
Do you mean you use fully qualified type names for all of your variables? That must become tedious after a while.
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
Not the "basic" ones with built-in aliases like int and string, but all the rest, yes.
It's my preference. It aids my memory.
|
|
|
|
|
There is also a setting that allows it to remove unused ones on build. Might keep you from manually deleting them.
HTH
Jack of all trades, master of none, though often times better than master of one.
|
|
|
|
|
Personally, I can't use that one either without extra configuration work.
The reason being is I often target the dotnet framework as well as the newer dotnet offerings, and the newer ones have things like System.Collections.Generic already implicitly declared. Sharing the source file between each would cause an error in the DNF version if the newer dotnet version of the project gets built.
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
And my IoT UI/User Experience library here:
https://honeythecodewitch.com/uix
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
