|
Even better if, like me, you work from home. A 5 second commute in whatever you feel like wearing today.
For some reason, your opening sentence reminded me of Alan Turing and working with mercury delay line (MDL) memory. Turing was all about efficiency, and his programs could figure out how long it would take for the MDL to return data, and would continue working on other things until the data was ready. Sort of a (very) early co-routine. Truly an amazing mind.
"A little song, a little dance, a little seltzer down your pants"
Chuckles the clown
|
|
|
|
|
My condolences! It's a chilly 67°F and sunny here.
Will Rogers never met me.
|
|
|
|
|
Pardon my curiosity  ... is -37C "normal" in Canada now ?
|
|
|
|
|
In this part of the Canada (Edmonton AB), it's not unknown. I seem to recall that as a teenager, we would see -40 most winters. Now, it seems that -35 is more common. Of course, as you go farther north it can get much colder.
"A little song, a little dance, a little seltzer down your pants"
Chuckles the clown
|
|
|
|
|
That is quite far away from any ocean or major lake, isn't it?
I grew up in an inland town in Norway. The winter air was so dry that you saw humidifiers in ever home. We hardly knew what wind felt like (except when skiing down a hill ). We didn't consider it 'real winter' until the temperature dropped below -20C.
Now I am living in a costal town. The air is usually quite humid, the winds can be strong, and most snow falls when temperature is around freezing, so it is wet and heavy. I am freezing much more here, at 0C, that I did in my home town at -20C. Wind and humidity has a tremendous impact on how cold it feels. The "wind chill factor" is very real for how you feel the cold. (Right now, the weather service reports -11C in my place, but due to the wind it "feels like -18C".
I am not used to -40C, though. We rarely had below -30C in my childhood. Even at -30C we were out romping in the snow. Chilly, sure. But 'cold'? Not if you were properly dressed. We knew how to dress up, and how to behave in the cold.
The biggest danger is not the cold in itself, but not knowing how to handle it. Shipping a Florida man to Edmonton at -40 should be done with care but I have no worries about Canadian natives.
Religious freedom is the freedom to say that two plus two make five.
|
|
|
|
|
|
I get attached my my mice and keyboards. Try to use the same setup on each system I use. The mouse specifically is a USB corded Razor; wireless just won't work for me - too much lag, and any lag irritates me. But my main beef is when mice lose their plastic slider pads. It always starts at one particular edge and snags the mousepad. A perfectly good mouse brought down by a .0001 cent part.
yes, I've tried the replacement path - it never seems to stick as well.
I'll go get some cheese with my wine. Buying a new mouse pad as well. The little things are important.
Charlie Gilley
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
Has never been more appropriate.
|
|
|
|
|
charlieg wrote: wireless just won't work for me - too much lag
That's amazing. I've used wireless mice for a long time, and have never noticed lag. Can you describe it?
Software Zen: delete this;
|
|
|
|
|
Gary R. Wheeler wrote: never noticed lag. Can you describe it?
It happened to me not long ago. I found that my mouse would stutter when I was using the left side of the mouse pad. My PC sits on the floor not more than 3 feet from the desk surface and mousepad. Luckily, I had a usb extender such that I could place the receiver on top of the desk and haven't had issues since.
"Go forth into the source" - Neal Morse
"Hope is contagious"
|
|
|
|
|
Hmm. It's understandable, but not an unavoidable defect in the technology. I've had good results even at distances of 3-4 feet, as long as they were line-of-sight. Barriers between the mouse and receiver shortened that distance.
Software Zen: delete this;
|
|
|
|
|
Must have been numerous retransmissions caused by low signal/much noise - the distance by itself does not cause any delay (well, in the nanosecond range, but any protocol handling overshadows that).
Like Gary R. Wheeler, I have been using wireless mice for many years, and never noticed any lag. I have a Dell screen with a built-in mini-hub with two sockets. That is really nice for memory sticks, phone charging and transferring photos and video from my mobile or camera. The other socket holds my wireless dongle, so I never have a problem with signal strength for the mouse and keyboard. That could be the reason why I never see any lag with either.
Religious freedom is the freedom to say that two plus two make five.
|
|
|
|
|
well I know one mouse likes to go to sleep all the time if I'm not using it constantly. And as others have said, there is some stutter. Might be the mice I've purchased.
Charlie Gilley
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
Has never been more appropriate.
|
|
|
|
|
This is my experience with Bluetooth mice, but normally not mice with a dedicated receiver.
This was supposed to have been fixed with some upgrade to the Bluetooth standard, but I could not tell you which one and I wouldn't know what standard my computer is running anyway.
|
|
|
|
|
lol - dedicated receiver. Where did I put that *** thing? But honestly, almost all of my usb ports are full, so I tend to avoid them.
Charlie Gilley
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
Has never been more appropriate.
|
|
|
|
|
I haven't seen a lag either. I have seen a stutter but that was either because the mouse was bad or new batteries were needed.
|
|
|
|
|
I own well used , maybe third handed wooden ugly desk
- AND no mouse pad.... KISS
|
|
|
|
|
The only time I've had lag in a wireless mouse or trackball is when it's dirty.
|
|
|
|
|
wired mouse and keyboard all the way. Minimum latency. No line of sight, issues. I have USB port on keyboard for mouse to reduce cable clutter. Perixx model TK566 keyboard. Cheap and has 2 USB ports.
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
jmaida wrote: wired mouse and keyboard all the way. Minimum latency. No line of sight, issues.
lol...well if there was a line of sight problem then you should check which universe you woke up in.
|
|
|
|
|
 actually had a line sight issue when the wireless mouse/keyboard USB interface (little USB pimple) on computer was sometimes blocked by a portable USB drive. Mouse and keyboard lost signals from time to time.
I have other issues with wireless mouse/keyboards, but this ended their use for me on my system.
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
jmaida wrote: No line of sight, issues.
But you do have line of USB cable issues 
(I like to retire to my recliner, keyboard in my lap, mouse on the armrest. That would require a USB extension cord, which would too easily be pulled out every time I swing my recliner around to put another log in the open fireplace, or pat the dog, or whatever. I know from experience (although that is long ago, but USB Extension cables haven't changed).)
Religious freedom is the freedom to say that two plus two make five.
|
|
|
|
|
 True, wires are wires of any length
I used Logitech wireless mouse and keyboard for years, but was problematic.
I upgraded but still issues.
I do not use a recliner (Lazy Boy as known in US),
but if I did, I would figure out a way to make wires work.
I may return to the wireless world, but happy right now.
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
I also have not noticed lag w/ my wireless mouse. re/ insistence I insist on softness and low coefficient of friction. I utilize a Teflon cloth atop a soft mouse pad w/ double sided sticky cloth betwixt and between also after market Teflon mouse feet. Much less friction than standard mouse pads. I am surprised the mouse and pad manufacturers do not utilize same.
|
|
|
|
|
Update: Thanks to Daniel asking me just the right question I figured out a way to hack my way around the lack of Span/ReadOnlySpan with Deslang by making a dummy with the same name and some appropriate stub methods. I don't actually use that code directly, but my Deslang engine does when it needs to resolve System.ReadOnlySpan<char> which again, it must do under the .NET Framework where that type doesn't otherwise exist. Deslang just needed to eat. 
So I'm still going to target the DNF. I may also provide a roslyn generator based alternative to using the codedom but it seems it's a bit of a learning curve, and more work given the tools I already have for CodeDOM stuff, like Deslang. Also it may require the end user to have more microsoft fluff installed and running in order to use it, so all that is something I need to run down. Progress!
_____________________________________________________________________________________
I don't know whether to target .NET Framework with my FA library anymore.
The issue is that you don't have spans in DNF, and now my regex stuff uses it to keep up with Microsoft's engine (which does the same thing)
This created a snowball of issues. For starters, I use a tool called Deslang to turn a subset of C# into a generic Abstract Syntax Tree that can be rendered into C#, VB.NET, or something else. I use this tool to prepackage shared code that I want to "generate" for the user in any language they specified.
The issue with building the AST directly is it's very verbose, taking a solid paragraph of code to declare a local variable. Deslang does it for me and produces code that has that AST already cooked into an object graph.
Deslang uses some reflection magic. And that magic is .NET Framework only. However, it cannot see ReadOnlySpan<char> because it's a span, and those don't exist in the DNF. 
Ergo, I cannot generate span code this way.
I'm currently using the codedom and thinking of moving over to the far more modern roslyn services and abandoning DNF altogether.
There's one issue though, and that is that if you were using my code generators to make build tools of your own, you won't be able to make self contained executables anymore because that's a .NET Framework feature only. The other cases have multiple files per assembly which makes their use as build tools a bit uglier. Not insurmountable, but less than ideal.
Still, in order to fully support the .NET framework at this point I'd have to fork my runtime string matcher code and my compiler plus my code generator too, all so I could generate a less performant, .NET Framework friendly alternative. I think this is basically what Microsoft does, but they have staff. I don't.
I really like the .NET Framework. I like Winforms. I like self contained executables. They do run on linux regardless of what microsoft says (except winforms of course) because Mono has supported DNF from the beginning.
I never really understood the need to make several more .NET "kinds", but I guess now that span doesn't work in the DNF I've got some hard choices to make.
Am I just getting old? This all seems like a lot of unnecessary trouble Microsoft made for people.
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
And my IoT UI/User Experience library here:
https://honeythecodewitch.com/uix
modified 14-Jan-24 11:22am.
|
|
|
|
|
I too like .NET as an environment, but as long as Microsoft is the only full implementor of the language and libraries, one is liable to run into the kind of issues that you mention. They are the only ones that specify the CLR, and everyone else must fall in line.
That is one of the reasons that I prefer to work in standardized languages such as C++. I know exactly what I'm getting (and not getting), and if a compiler implementor decides not to support part of the Standard, there are other fish in the sea.
Could you not create a wrapper around the parts of Microsoft's DNF that you need, providing the same functionality where it exists, but your own implementation where it doesn't? That would at least allow the rest of your code to remain unchanged.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
