abraxas @ abraxas @lemmy.ml

Posts

1

Comments

387

Joined

2 yr. ago

Totally fair. I think I'm sticking with Webstorm for at least one more year, but might someday give VSCode another try.

Webstorm was the combobreaker that ended my 15 years of Vim.

I think that's true of all editors, though. I ended up on the intellij side of things, and it means I'm clueless about VSCode's key patterns. I've only picked up ctrl-p so far, and keep having to remind myself "this is shift-shift in Microsoft"

I don't really disagree with what you're saying, but I have a point we should agree on. Your previous discussion point spoke to ethics or morality, to "rules" even between enemies. Your current rebuttal is instead one of pragmatism.

I agree it may not be pragmatic to respond fully to Russia as would be entirely just. The Nuremburg trials were entirely just (at least in my view), but nobody doubts there are hundreds of rulers that get handshakes instead of a death conviction based entirely on the unreasonable cost, paid by innocents, of doing the right thing.

The rules at this point suggest Putin should have been stripped of all power and prosecuted by Ukraine. Military conquest is simply unacceptable on the world stage, and that does (or should) apply to all governments at this point. But rules are often only followed when possible and best for everyone

I think that's a hard question. Node definitely helped evolve it. The idea of isomorphism was slow-growing (and yes, originally pretty rocky), but foundational to what we now see as web development. But if I really had to describe the start of the "JS obsession" by my experience, it would be the AJAX explosion, which led to the advent of the "web-based app". That very first moment of realization that yes, you can do anything on the web. It might be hard for a developer who started after that time, but functionality used to be relegated to windowed and console apps. In that world, you could imagine how useless javascript must have seemed - why do I need to write code to give "functionality" to what was basically seen as a remote pdf?

But then, I think there's no surprise to the fact every big company under the sun has some critical contribution to server-side javascript. Back then, most of the dev world were using Perl, Python, Ruby, PHP for their web backends (Java, VB, and C# were used, but too damn hard to write in). At best, those languages were non-ideal but reasonably comparable to javascript. At worst, some of those languages (Perl, lookin at you) were worse than javascript at all the reasons people make fun of javascript now.

It took a while to kick Rails off the "next big thing" podium, but it was pretty quick that Node was showing offerings that were just better than Perl-catalyst or early Python-Django. It's funny, Rails was the one with fancy ways to ship javascript from server routes (what a shit show that tech was) back when Node was establishing new best practices on non-isomorphic web apps. I remember when Hapi first came out, backed by Walmart. I then went from being a node hobbiest to believing it was the future. 1 year later I was running a scrappy little node team and we had this little $10M+ telephony app (of all things).

Ah, yeah. Pretty awesome. Looks like they added that in 2019. I wonder why I've not seen that behavior used much at all.

Is there also good repo-mirror functionality to keep it easy to curate the private source?

I happened to be a fullstack developer when the transition happened, so I saw it firsthand. I would say it predated V8 by a year or two. By the time V8 came out, I was already writing plenty of (simple) javascript for applications.

I would say it was more about plugged security holes and Ajax becoming more viable for real-world use. The "don't ever use javascript" rule came from people disabling javascript because javascript was being used for malware. V8 was a part of that transition and growth, but at least in my memory not the shot that started it all.

There were developers (and books) pushing Rails+Ajax pretty hard in 2007, a full year before V8's first release in September of 2008.

The answer to the paradox of tolerance is usually “the one fighting for peaceful coexistence is in the right”.

I mean, every action a police officer takes in any country parallels to some of the worst crimes imaginable. An armed person saying “You are not allowed to leave” is a felony in my country punishable by up to life imprisonment. While people argue about problems with police behavior or severity of criminal penalties, it is generally agreed upon that an arrest of a suspected violent offender is always less severe than civilian kidnapping.

And perhaps outside of the police, for every person I’ve met who is so anti-cop they consider arresting even a serial-killer unacceptable, I have found common ground of some severe behavior they feel is only rightly done by the party trying to find a peaceful coexistance.

I didn't think anyone was using easy_install anymore, but I still see it in docs for stuff.

Poetry looks interesting, but does it support private-only dependencies, where the system will reject a library or version if it has not been previously approved and cached?

So let's say I want to add a library not currently being used in this project, but that might have been approved for another project in another repo? How does pip freeze solve that problem? Do python users endorse a "every single python app in the entire org should use the same requirements.txt" mindset? Or what am I missing?

How so? The companies I worked for were using venv's but nothing that could help with standards.

Using a private npm repo, I can actually do aninstall of a library I want to use and it'll refuse to install if that library isn't already approved for use by the organization, and if it is/does, it will install only the approved version. Further, I still don't have any of the libraries installed I don't want (even secure-seeming unnecessary code is a potential risk and unnecessary). The last 2 places I worked that used python used venv's, but the pip requirements.txt file was still fairly hard to keep regulated.

Yeah, the only way defederation is a feature is if there's a way (even if it's standardized at the client-side) to merge that defederation for those who want a cohesive experience.

It'd almost be better if every user could pick their own "federations" instead of it being at the server level. Obviously the servers need to have that control and my hypothetical might not be in throwing range of what lemmy can/should do.

You're right about python being the same. Python doesn't have a mature alternative to Typescript that launches it into having best-in-class type handling.

There's so much that my C# devs can't do with its horrible type system that Typescript "just does better". At compile-time at least.

I used to work on a hybrid typescript/python product (some services js, some TS, some python), and the TS stuff was just faster-running, easier to iterate, and better. And story-point allocations consistently showed that for an excess of 20 devs working on those codebases.

As for pip/easy_install vs npm/yarn/pnpm... I'm curious what you think pip does well that yarn/npm doesn't? I'll say in my work experience there's more/better enterprise private repository/cache support for node modules than for python modules. Using npm security databases alongside "known good versioning" allows a team of even 100 developers to safely add libraries to projects with no fear of falling out of corporate compliance regulations. I've never seen that implemented with pip

even though I am guessing that with a better webassembly support of the browsers

Considering V8 overcame python in benchmarks nearly a decade ago, I'm not sure even some miraculous webassembly environment would put python faster than javascript in the browser of all places.

V8 does not quite compete with the big guns in the space (C, Rust, Go), but now that it's only 2-4x slower than C++, it's created this niche of "almost hardcore fast" for javascript that is just unlikely to be dethroned any time soon.

People fail to quite get how many leaps and bounds V8 has taken in the last 10-12 years. Javascript's reputation of being "scripting language slow" is simply no longer the case and hasn't been for an entire Era in software terms. Reasonably-written Javascript is now often faster than heavily-tuned Python, and well-written javascript is faster than reasonably-written C++. It's not necessarily fair (like comparing modern solar to nuclear, with the absurd amount of money that's gone into solar research), but I don't see it changing any time soon.

So bizarre how life experience drives attitude. I'm one of those who has worked in a dozen languages, and Javascript (well, Typescript now) simply wins out for me. I run a C# team right now (have been for nearly a decade), and I can say as much as I love my job I hate the language. We get less done with slower code and with more bugs and more (very talented) people than the little $10M operation 4 of us did with node.js a couple jobs ago.

And as an aftethought since language and tooling are different topics... the ops toolchains for javascript are so much better than anything I've worked in any other language. Code released to production often ends up costing us less (dollar value) in the time to deploy, and then less per-user and per-hour.

I know a lot of C# diehards and I respect their passion. I just cannot relate to their experience. And I can say that with over a decade of experience in many of the languages in the original meme.

It was when better sandboxing came out and the only valid complaints about javascript became invalid.

I was there. It was a good time.

sealioning question

I figured as much (though the term is new to me). Giving a solid answer is often the right response to that kind of question. Every propaganda technique has a weakness, and "hard questions"'s weakness is that people usually read the replies and if those replies are calm and collected recitations of facts, people hear them and the question's bullshit value is mitigated.

Trans folk still identify as Trans indefinitely in about 94% of cases. Evidence suggests many of the other 6% are bullied, harassed, or threatened as a factor in their changing the way they identify.

Or was that a rhetorical question?

I kinda thought I'd stop hearing the constant bad-faith accusations when I left reddit. I suppose not.

Just went to the Delta site and checked my state. The ONLY plan in my state they have that covers non-trivial work is $60/mo with a maximum coverage of $1000. The 80% (I know Delta employees... no dentist I would use is in their network) coverage after copay is nice, but you're still paying $700+ out of pocket for a potential $1000 total coverage. And unless you think I'm lying about the "Uninsured discount", it means if my dentist gives me a $300 discount on work for being uninsured (they do), I still end up ahead.

So thank you for implying I'm lying and then giving me the directions to prove my point.

In addition, I’m pretty sure people are straight up making up stuff. Spending $700 before you break even on dental insurance is straight up fiction.

My last two companies, the dental plan was $50/mo (or a total of $600/yr). Other than having only a $25 copay for cleaning, it was between 10% and 20% coinsure with a $1000 limit.

That means optimistically, I needed to spend about $2500 to break even on the most optimistic coinsure, and my benefits disappeared after I spent $5000 (and only would cost the insurance company $400 if I spent every penny).

I literally mathed it out in a year I needed 2 root canals and it would have been cheaper to NOT have the plan. And that was before I discovered the fact my office had special "uninsured assistance" that wasn't driven by income.

Many Dental plans are an absolute scam. Part of the problem on them is that most people in some areas ONLY get dental insurance if they know they're going to need it. Makes it hard to have a price that works. It's part of why I have always supported government-paid insurance for medical and dental issues.