That's good to know. I suppose that would probably be the cleanest way of doing it. Thank you!
702 karma · joined September 16, 2016
That's good to know. I suppose that would probably be the cleanest way of doing it. Thank you!
There's definitely some nice stuff about it, but there's also some stuff that's a bit of a pain. For one thing, being straight up unable to compile a program if there's an unused variable, not even a debug compiler flag or anything to allow it while testing. There's a lot of cases where I just want to move one thing around, or I'm partway through writing a function and just want to see what state something is in at a point, so I want to throw a breakpoint on a line and run the program up to that point. But even though my code is technically all valid, because the variable I want to look at is unused, or I commented out a line that makes something else unused, I now can't compile at all. So there's a lot of times I'll have to throw in a random fmt.Print of a random property of index zero of an array or something, which might crash anyway if it's reached, but at least it'll compile. It maybe doesn't seem like it would be that big of a deal, but when you've got a train of thought going, and you're trying to iterate fast, it can really pull you out of the flow of things.
There's also a lot of weird situations where I find it hard to keep things clean. For instance, I like using this shorthand:
if err := doThing(bar); err != nil {
// handle error
}
But if you're doing it in a case where your function returns a result and an error, i.e. if foo, err := doThing(bar); err != nil {
// handle error
}
That's indeed valid code, but foo only exists in the scope of that error handling. So you'd have to declare it above with its type var foo FooType
if foo, err := doThing(bar); err != nil {
// handle error
}
But you can't actually do this because when using type inference, both return values have to not be declared beforehand. So you have to pull err out into a declared var with a type, and remove the type inference altogether like this var foo FooType
var err Error
if foo, err = doThing(bar); err != nil {
// handle error
}
And from that point on, if you're using this pattern again anywhere else below in that function and you want to continue using that slick error handling shorthand, there's barely any point because err already exists in your scope, and you'd just be redeclaring it.Perhaps there's some tricks I don't know about, but I tend to run into situations like this a lot, and I spend so much time trying to appease weird edge-cases of the compiler's strict rules that is really throws a wrench in my workflow.
I think that's honestly a bigger issue than paragraph width
I just check with Firefox which he was complaining about, and while it doesn't do this, it at least by default prompts you to confirm you want to close multiple tabs which should hopefully prevent you from quitting out by accident.
I'm not really sure how they measure resolution with this, that could still just be a mistake. But I do know e-ink displays sacrifice resolution for that colour with current technology.
But people who were in debt are doing great!
It happens occasionally that their servers go down and nobody is able to stream anything. I don't know why their servers are a dependancy in that chain at all, I probably looked it up before but I don't recall it being a good reason.
Ideally it would be nice if you could opt yourself out of having any conversations backed up, but I'm sure to Apple the privacy benefits doesn't outweigh the amount of customer support hours that would be wasted explaining to people why some of their conversations aren't transferring to their new iPhone.
There aren't any bugs as long as I don't look for them!
Just the last week a musician tweeted something dumb about making his daughter learn how to use a can opener to open beans, and within a day, the very successful podcast he did the theme song for, where his track was used for the past like 10 years disowned him and stopped using the song. Then he was kicked off the cruise gathering where he was good friends with the guy who ran it and has been a regular headliner for years.
The internet has created a culture problem that I'm not convinced decentralized social networks will fix. At best, if one was created that people actually used, we wouldn't have situations we've seen with Alex Jones and Trump where all the platforms unperson someone on the same day, cause they could still at least keep their audience on the decentralized platform.
I read the article and he claims it does? It's just that the default uses their cloud backup where Telegram has access to the private keys.
The last paragraph basically claims "it's not working from bed that's bad, it's the stigma against working from bed that's bad!"
It's not necessarily anything new for Google though. I remember for years on YouTube there would be a giant square ad to the right of YouTube videos that would pop in after a few seconds and push the recommended videos all down, so you'd frequently go to click a video and suddenly an ad pops under your cursor and you click that instead
There's a tool called Everything that somehow does a search across all files instantaneously and I haven't touched start since then
Reading that subreddit is a guilty pleasure of mine. It reminds me a lot of how the Windows Phone subreddit was while that was still around.
It's how they found an old unused Luigi model for Mario 64!
The book burning going on lately is insane
I live in a place with a fairly small population, and I got offers at 3/3 programming jobs I've applied for since my first in 2017.
I think if the power of a computer is put at your fingertips and you don't want to dig deeper, or see what else you're capable of creating, that's just how it is. I don't think it's any different from how some people never get into sports. It's fine to introduce kids to it and I'm sure it'll take with some of them, but there's no need to force it any more than you would with any other field.