|
I purchased a flat 34" ultra wide. Mainly use it for write code (development). The monitor supported picture-by-picture. I really like it a lot. Depending where I'm sitting, it feels like the text on either ends are harder to read. Guessing cause I'm viewing from the side.
Haven't tried a curved, so not able to give an opinion. Getting it would help, who knows.
|
|
|
|
|
luckydragon76 wrote: Depending where I'm sitting, it feels like the text on either ends are harder to read. Right. Which is why I'm leaning towards a curved screen.
/ravi
|
|
|
|
|
|
|
Sadly, that one took a few seconds to process! Good one!
"Go forth into the source" - Neal Morse
"Hope is contagious"
|
|
|
|
|
I made it up myself, too!
|
|
|
|
|
So...web developers are the new VB developers?
|
|
|
|
|
That's kinda rude to web developers.
Except for PHP ones, obviously.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
I wouldn't know, I drive a Cadillac 😉
|
|
|
|
|
I have my kid drive. yep.
|
|
|
|
|
I'm 72 and drive a Honda HRV, when I am not going someplace with SWMBO.
with the price of Gas these days, I'm not driving much, anywhere.
VB haters are going to hate...
down by the river - Neil Young
|
|
|
|
|
I'm 58, and drive a 2003 Ford Focus ZX5 (original owner) to work, but keep a 2018 Porsche Macan GTS in the garage for fun. Thinking about replacing the Focus with a used Prius or new Tesla soon. I also own a 2006 Honda Civic as well that I need to dump soon; nothing wrong with it, just can't stand driving it.
I looked at cars for about 5 years. Subaru WRX, BMW M series, Honda Civic SI, Mercedes and passed on them. The BMW X3 M series is nice. Now days, you can't buy a decent car for under $45K when you consider the quality of the parts and how easy the parts break or fail. I think the Tesla Model 3 will be the next Honda Civic and be that popular. But the Tesla Dual Motors are much better overall in terms of power and performance.
As my friends said, your car expresses who you are.
If it ain't broke don't fix it
Discover my world at jkirkerx.com
|
|
|
|
|
yeah, that`s what it comes down to, that`s the core doctrine.
|
|
|
|
|
Not whinged about MS for a while, so here goes...
I'm doing lots of work with mapping and webservices, and had (for simplicity) created a basic DTO object called LatLng, consisting of just a Latitude and Longitude property. Then I discovered that MS had an object GeoCoordinate (in System.Device.Location) that had LatLng and also a method for calculating distance to another LatLng. I already had that formula but thought I'd simplify my code by using the GeoCoordinate object and it's DistanceFrom function. Simple - pull out my LatLng class, replace with GeoCoordinate, all good. Everything worked from the start.
Until... I needed to access the LatLng data from a webservice, using JSON. The webservice ran fine, but JQuery wouldn't parse the JSON. Turns out that the GeoCoordinate object has some properties, defined as Double, that default to NaN - NOT zero! When the webservice serializes the object to JSON, it does it as {"Latitude" : NaN} which the browser can't parse as valid JSON, so the whole thing is unreadable. Those properties include Altitude, Speed, HorizontalAccuracy and VerticalAccuracy.
Now, I use the GeoCoordinate in so many places I don't want to explicitly set all these properties (which I don't even need anyway). So I subclassed GeoCoordinate, wrapping it in my own class and setting those four values to 0 in the constructor. All good, surely? Nope, still not working in the JSON serialisation. Close inspection showed that Altitude and Speed were now zero, but the accuracy properties still coming back as NaN. Checked the documentation, confirmed those properties are settable. Setting the value to 1 is all good, but setting it to 0 "works" (as in no error thrown) but the value remains as NaN.
Now, I sort-of understand why you can't have an accuracy of zero in this context... but WHY Microsoft, don't you either throw an exception or at least DOCUMENT that??? (The property even has a documented "Out of Range" exception, but they don't throw it for zero )
So two oddities - failing to parse the JSON because of an unquoted text literal "NaN", and a property with an undocumented un-settable value. Wasted the best part of the afternoon...
(And on the subject of rants, CodeProject seems to have lost the toolbar when making posts in a forum...)
|
|
|
|
|
DerekT-P wrote: GeoCoordinate object has some properties, defined as Double, that default to NaN - NOT zero! Can you tell me what would those values be for someone driving in Denmark at sealevel, at a stop sign while traveling due North?
|
|
|
|
|
More to the point, someone on the equator due south of Greenwich.
I was more taken aback that the serialiser generates non-parseable JSON from a "valid" GeoCoordinate object, tbh.
|
|
|
|
|
Yep,
I covered altitude, speed and heading. Realized after I posted that I should have used a city on the prime meridian for that extra kick.
DerekT-P wrote: I was more taken aback that the serialiser generates non-parseable JSON I think you might find that some people are surprised that you are trying to serialize an uninitialized object.
|
|
|
|
|
This is all documented in the docs for the GeoCoordinate class, which isn't serializable. The serialization/deserialization code needs to handle the NaNs to ensure uninitialized data is properly converted. Serializing a NaN to a number is not correct. NaN isn't an out of range error, it's simply not initialized. These are different concepts.
|
|
|
|
|
I can find a Microsoft document that does indeed state the constructor with no parameters creates an instance "with no fields set". The description of other constructors (e.g. passing lat/lng values) does not mention that other fields are not set. In this case, GeoCoordinate uses NaN to mean "unknown". I feel it would make more sense to use double? (i.e. nullable) values anyway - which would also be supported by JSON.
However my main gripe is not that the fields are NaN, but that ASP.Net fails to serialise NaN values in a way that makes the output JSON invalid. Valid input should not generate invalid output. I recognise (belatedly!) that NaN is itself not supported by JSON but that doesn't change the fact that valid input should generate valid output. If it's unable to do so it should throw an exception, surely?
My other gripe is that the Accuracy fields are documented as Double, yet they are clearly not a "true" Double. You can assign a valid double value to it (i.e. zero) and yet after the assignment the value remains NaN. This is not the normal behaviour of a Double and as such it would be really, really, really helpful if it were documented. You can set it successfully to .000000000000001 but not to zero. It makes you wonder if there are other values it can't have...? (Oh, and I tried setting it to a negative value, just to see what happens; and it crashed the IIS Application Pool. It's now showing as "Stopped" but won't accept Start! Guess that's it's way of telling me to go to bed... )
|
|
|
|
|
|
Here's link to Google Maps showing what you're asking to be the defaults:
Google Maps
|
|
|
|
|
Here's the source of those two properties[^]
What do you get when you cross a joke with a rhetorical question?
The metaphorical solid rear-end expulsions have impacted the metaphorical motorized bladed rotating air movement mechanism.
Do questions with multiple question marks annoy you???
|
|
|
|
|
Microsoft's business model is to grind you down and break you, make you realize that hope is a luxury you can't afford and that any attempt at resistance is futile.
To err is human. Fortune favors the monsters.
|
|
|
|
|
...meet in the hallway.
One asks the other: Can't you sleep either?
|
|
|
|
|
Cuz they're corrupt? Or...?
|
|
|
|