shortstuffsushi

The problem is that most of the "bad" JS violators aren't building data viz, they're doing something much less complicated with the same tools.

Edit: the article mentions CNN, which is a mostly "static" site, but has enough JS to take 13 seconds to load on the "average" phone.

I'm seeing in the source that the author prefers

type

methodName(args...)

Is this a common C-ism? I'm not familiar with this code style.

Yeah, because I've created issues with the Brave browser, my first 8 suggestions were other Brave repos. Not useful for me.

> even though we all have bigger/high-res screens with more real estate than ever.

I'm not disagreeing with you, but is this perhaps the reason why this is happening? If we have so much more space, we've got room for extra big bars. If we get higher resolutions, smaller fonts are (possibly) harder to read, so we make them bigger.

Maybe I'm just making stuff up, though.

They're referencing the article, I believe.

Could you explain the limitations? Why specifically 3 servers or 24 cpus? Totally arbitrary numbers, or linked to something?

I think that the Mozilla Dev docs would probably be useful to you, or at least that's what I always end up going to -- https://developer.mozilla.org/en-US/

Huh, TIL I guess. I've only barely messed with that, and it most have just been on "recent enough" versions to support array functions.

Why do you need the [ ... elements ] -- can't you call foreach off elements directly? Is it not an array?

Huh, I have enjoyed this site in the past, but I forgot about the code comparisons including script tags for non-Vanilla and not for Vanilla. That seems a bit misleading. I get the extra script tag for jQuery, but the <script> { content } </script> would still be necessary for vanilla..

Could you mention what you're likely to be printing? What sort of uses do you have where you write notes in a plain text editor and print them out? I can't think of the last time I printed anything -- actually, I should say I can't think of the last time that I printed anything that wasn't a contract or HR paperwork type of stuff, which is never in plain text. I'm curious what else is still being printed these days. Also, they have plugins for that, if you're interested. You're correct that it's not built in, though.

Is this not just a matter of "the joke of the times?" Whatever is currently trendy can almost certainly be found referenced in every front page thread. Currently it's DJT, previously it was the FPH, etc. The masses shift targets, but fixating on a current trend seems pretty steady.

What would the flat tax actually tax though, income? Wouldn't they just dodge that then by not having income? Sure, for you and me it would make it easier -- my W2 says I made exactly 100k, here's exactly 50k of it, period. For people who have a flexible income, why report any amount that would make you pay in?

What is "class-of-service?" I'm not familiar with this term.

I'm confused, how is it server less if it literally had a server.py file that acts as an HTTP server? I'm not sure, but it appears it may also expect to run in Docker, for another layer of complexity. Finally, why this vs any other editor? What advantage does it offer, especially if the first two assumptions in this post are accurate?

It seems to also be a sort of repl or something that evaluates the code you write as you write it maybe? I'd have to look at this from my computer to understand, but it's not what I expected from the title.

I was coming to the comments in search of what 100x meant -- how it was measured and compared. If someone is 100x more productive, they ought to be able to build systems in days or weeks instead of years, right? Kind of joking, but mostly poking fun at what seem like silly numbers.

I was coming here just now to see what others thought about this. I see the idea of an open, issue and pull request-able privacy policy as a really neat idea. It additionally gives you a full history of the changes made to it, because git. This seems like a cool choice by GitHub.

You're not wrong, this does give up that sort of control. That's a different issue, but certainly a reason why they might not want to do it.

Why would their API need to be anything more than what they offer to their app? Why not something like "hey, you can use our stuff, but you've only got access to the same set of APIs we use in our app, and we may change it as we please.

Oh btw, here are the auto-gen'd docs, hope those are enough"

That seems like it'd be both developer friendly and no more maintenance than they're already putting into it. The alternative is basically things like this, where someone figures it out anyway, and we have to wait and see if they play it cool, or take it badly and make the author take it down.

This is super interesting, especially the part about trying to reverse engineer their "security" measure. I did something like this a few months back for Paylocity, a time logging system that has a terrible web interface. After trying to talk with their sales people about them potentially offering an API, I was told "no API, just this mobile app." Turns out the mobile app is just an Ionic app with all of the resources (all, including tests and even test environment logins and stuff) baked in. Super easy to grab their API out of that (literally called /mobileapi/), but then the trouble was figuring out how they generated their security token header, which was also a little dance of timestamps and faked device info.

The best part was when I contacted them afterwards and warned them about the extra pieces of info they had baked in, their response was basically "yeah, we're aware that there's more in there than there should be, but it's not a priority." Oh well, they just have all of my personal information.

> I want proof. I only see numbers. Everything else is conjecture.

But wait, is this not conjecture, since it doesn't currently exist? Sure, you have sources where it has worked, but the proof would only be implementing it here.

> Or is the US government not a leading force in fighting corruption anymore?

What? I don't understand what you're getting at here. My point isn't that the government is corrupt, it's that it's inefficient.

This simplification seems disingenuous. Would switching to single payer solve your last sentence / quote from the article? Aka, would putting the US government in the middle make things simpler and more efficient (and cheaper) for the end user (health care patients)? I can't say I'm convinced.

Compare with the current system, where any given user is still effectively dealing with a single payer -- their insurance provider. Their insurance provider is one level of removal from the health system that has to be paid.

Now, the idea of transparency? That's lovely, and would force accountability and that sort of thing which could potentially have impact. I can't disagree with that. I'm not sure that just putting the government in the middle fixes that either, though.

As /u/frgtpsswrdlame points out, we have the most expensive health care, which seems like the bigger issue that isn't addressed. If we lessened the cost of health care in the US, that would probably be a better start, imo. Does single payer fix that? I would think that private, competing companies would seek out better deals vs a single government entity who couldn't really negotiate, but perhaps I've got that backwards.

I'm not disagreeing with the thought on the whole, I just don't see how single payer fixes these problems.

The wiki strikes me as similar to GitHubs wiki / pages stuff (which seems obvious enough). Which I appreciate the features it offers (markdown, git, etc), I don't feel like the majority of people using Confluence would, and the feature set is indeed fairly different. Not bad, and I would certainly use it, but I'm not sure it's a replacement for Confluence users.

The issue board on the other hand seems a lot closer to a "replacement" for Jira. The tag based concept reminds me (again) of a Github 3rd party tool, but it's nice that it's built in. Again, less feature-rich compared to Jira, but in this case, not necessarily a bad thing. Jira can be overboard for most workflows. I might have to give that a try.

It's here -- https://www.atlassian.com/licensing/cloud/future-pricing

Actual non-loaded question, does GitLab offer a wiki like Confluence and a full issue planning / management feature like Jira? I've only used a small amount of GitLab, and it was purely for code hosting, so I don't know.

They're still people that enjoy flavor, and a basil plant is pretty "easy" in terms of adding flavor to any food.

Have you found an alternative that works more consistently?

I guess this was the biggest question answering piece to me. When I think of a black hole, I assume it has a gigantic mass, enough that it's always the most massive local object, and subsequently pulls in all other things. I didn't realize that might not be the case. As black holes "absorb" everything that "falls" into them, do they continue to build mass then?

Somewhat naive questions, as I know very little about astronomy. Do black holes "move?" How is it that they could merge if they're stationary, unless they're pulling each other in I guess? If black holes are indeed pulling in everything, does that mean the whole universe would eventually be one giant black hole?

I gave you a clear set of reasons I dislike and will not use Cordova, but I feel like you're just using it as a shield. I mean seriously, Cordova is the reason you're not a "drone in an office?" Give me a break. How about all the people who are using Cordova in their Agile drone office? It's great that you've been able to get into your own thing, but plenty of, for instance, native mobile devs have done the same. Or non mobile devs. Or full stack. Heck, I too have written, by myself, native Android and iOS apps, and their backends. I don't think that's saying a whole lot.

Where did I say I was touching generated code, the cordova.js thing? Because I was trying to find the cause of our slow load in the app and stumbled through their init process into that issue.

The native plugins are usually good, as you mentioned, but don't cover more complex use cases. No, I'm not going to go through and talk about all of them -- this is two or three years ago now. We wrote native plugins for the features we needed that weren't available for our use cases, and it seems likely that any advanced app will end up needing to.

Your point about "compounding pain" is exactly how I feel about Cordova, because as I mentioned, it's as complex if not more in a hybrid app. You're fighting the build system, the js engine, the layout engine, etc. It's not as though you get it all for free because it's javascript.

It's great to enjoy your tools, and again, I'm glad you're able to make an independent living off it, but to claim that it's some sort of life changing tool the whole mobile world needs to take more seriously isn't realistic. And again, as far as new development, I'd love to hear people who are considering going the hybrid route chime in, but I at least don't know of anyone or any companies who are or would go that route.