throwaway43234

I think a good compromise is warnings aren't allowed in the final committed code (this can be enforced either by convention or with git hooks), but whatever you do locally is between you and your compiler. "What happens in the devbox stays in the devbox"

> that is actionable for a lot of people

Really hoping this is better by the next few months or my Seattle winter will be even more pill popping to maintain basic human functionality....

Right - I understand all that, I just think it's not a good idea. The compiler makers made some things warnings and others errors for a reason, to disregard their input because you have some idea that "warnings are just as bad as errors and should never be permitted in even dev builds of my very highly precious code" is to me a sign of an over-controlling "principle engineer" somewhere behind the scenes that doesn't trust their team, which is not a work environment I'd want to be in. (In the go case, the over-controlling principle engineers creating a work environment I'm not interested in participating in are the language designers themselves!)

I introduce unused variables all the time when I'm debugging/exploring, which always get cleaned up before commit (this is programmatically enforced, which I think is reasonable), to need to go and comment out the declarations for each variable that goes unused if I comment out a section, just because some "principle engineer" somewhere on my team (or the language design team) thinks unused variables are the devil reincarnate and can't be allowed in any build whatsoever is frankly insane. (Don't even get me started on cases where commenting out the declarations changes behavior...)

Or just ignore warnings if you know they're from a temporary change that wont ever be committed?

Most of "feeling sick" isn't the actual bacteria/virus causing problems, it's your immune system doing things like raising your internal temperature to fight off the virus or generating boatloads of phlegm to do whatever that does.

Some in stocks, some in banks, some in bonds, some in real estate, some in precious metals, etc.

Good reason to pull all crypto into fiat ASAP, store it in a real bank (or really, diversify it - user said that was the "vast vast majority" of their savings, that should never be all in one asset), and report it as other income on your taxes.

Is that really your bar for being "somewhat technically literate"? Being familiar with decentralized chat protocols and services? What a world...

I agree it's probably a joke, but I'm not so sure that the core idea is actually impossible... I could reasonably see a SaaS that simply provides a quick and dirty key-val store. The code is just a translation from REST to REDIS which could easily be done in 2 lines, the value-add is the hosting.

That'd actually be pretty helpful for initial prototyping, where you want to have state shared across devices but don't want to bother with hosting a backend at first, and localhost wont work because the client wants to play with it too.

Hasn't been touched in over a year. https://github.com/KeliLanguage

Curious, whats so special about SFO? I searched for some images and it doesn't seem terribly special (certainly not 2x price special).

If you take to time to set up incremental compilation, it's really quite fast. For reference, updates to the vscode repo (~5k files) take generally <300ms to recompile, and even incrementally updating after pulling in a batch of hundreds of commits takes only ~10 seconds.

It's concerning to me that the deno folks chose giving up on type safety over figuring out how to set up their development environment to better meet their needs.

These aren't signatures though? They're checksums, anyone could make them for any blob they want.

Is it a common scenario nowadays to download a file and have it be corrupted? I don't think I've ever had that happen (Though perhaps I wouldn't know, because I don't use these checksums! Though if a package is corrupted and it doesn't noticeably degrade, is it really corrupted? Hm... philosophy of internet downloads)

I've always been a bit confused as to what the attack vector those protect against is for self-hosted packages (i.e. not torrents, third party hosting services, etc.). If the attacker is able to coerce the web server into sending a compromised package when you `GET https://dl.google.com/go/go1.15.src.tar.gz`, couldn't they just as easily send a compromised checksum when you `GET https://golang.org/dl/`?

Blood Meridian is generally more highly regarded, no? Wiki states it's widely regarded as his magnum opus and a "Great American Novel".

Indeed, I've had mostly positive experiences with Isadora in the audio/video signal processing visual scripting space.

What do you find painful about it? Have you tried the new vscode javascript debugger? It makes things fairly easy - I'd say the main issue is loss of local variables in async stack frames (which makes sense, unless they're closed they're gone), but that's not typically too big of a concern IMO.

I understand that this is standard practice by now, but this is one of those cases where I can't help but feel the language design team strayed too far from the original spirit of python. Now there's yet another possible interpretation of an asterisk: multiplication; splatting; exponentiation; declaring variadic arguments; and now declaring that all subsequently declared arguments are to be keyword-only. And I understand that it sort-of relates to declaring variadic arguments, but it certainly isn't declaring variadic arguments, and in my opinion reusing the same token in the same syntactic construct for two wildly different purposes is destined to cause confusion. For evidence, see the other replies: people don't know about this and can't easily tell what it does. This runs counter to the Zen: "Readability counts", "Explicit is better than implicit", "Special cases aren't special enough to break the rules.", etc.

I think JavaScript got this right where the semantic resolution steps of arguments pretty closely follow the steps for assignment, which means once someone understands the basic idea of object destructuring they get named arguments for free, in the form of destructured object parameters:

    const foo = (positionalArg1, {namedArg1, namedArg2 = 'foo'}) => { ... }
    foo(1, {namedArg: 'bar'}) 
    // resolved same as 
    const [positionalArg1, {namedArg, namedArg2 = 'foo'}] = [1, {namedArg: 'bar'}]

right, it's not only compromised API keys, but it could be that with something else.

Nicotine has also been said to help fight the disease. French doctors have been given patches. Some study apparently showing smokers are 80% less likely to develop severe symptoms.

https://www.jpost.com/health-science/smoking-appears-to-prot...

Parent takes the posted-from metadata as absolute truth.

I say it can't be relied upon when an active & involved hack is underway.

You provide nothing of value. What do you think this entire thread is, but for idle speculation?

To be fair, it's still higher than yesterday's low. It's not like TWTR is known to increase over time anyways.

Its not hard to fathom that someone who was able to pull off a hack like this could have also found a way to mess with the metadata there.

Its not hard to believe that a group with the ability to hijack the twitter accounts of some of the world's most influential people could also hijack the "posted by" metadata.

Exactly. This difference between "we're only going to update the status page if a customer comes screaming to us that the service has been unavailable for the past 24 hours and they've received no updates" and "we have automated systems in place to updated the status page if the p95 response time exceeds XXX (among other things)".

Do you trust the service with the statuspage that is 100% green for all of history or the one that reports the occasional degradation?

Lol... always amusing when someone asks HNers what changes they'd like to see and why, and they respond with crazy analogies that are totally unactionable... not the first time this has happened, won't be the last.

What are the second order effects? What's this "complex reality" you're living in? VSCode gives you a log of every telemetry event it sends, none contain PII (if they do that'd be a serious issue and should be reported) and it provides a settings page to list and opt-out of every online service (including telemetry).

> notification queues ... which can add to an employees distraction load and decrease productivity when compared to a more basic code-host.

If you think your employees would be less productive if they didn't have a queue of work items to address and co-worker comments to look at and respond to... let's just I wouldn't work at your shop. You running a room full of air-gapped code production units or something?