igreulich

I buy the best camera an iPhone will give me. If that same camera in the Pro Max was in the Mini I would have bough that.

The iPhone 5 was the perfect size, and I miss that form factor. But The camera is what sells me the device.

Calling it a compiler is not great IMO, but it is a js bundler/transpiler.

You set it up, and write your js code, and parcel spits out the final, ready to embed in your html file, js and css assets.

That's oversimplified, but the basics all the same.

Aren't swans just geese in nicer clothes?

I would venture to guess that often it is because the answer is 'business reasons', which is often not reasonable.

For websites, as opposed to webapps, this might be fine. But a webapp will pretty nearly alawys want to look the same cross platform, sort of forcing styling.

I get it, they didn't like what they looked like before, because reasons. But I wonder what percentage of sites and apps were using unstyled controls.

Honestly, it read like they stopped because it was harder then they wanted to pay for. Or at least the next step would have been.

Being better than [x] does not make Slack good, per se. It might make some thankful they aren't using [x], but that's really about as far as that should go.

I like Slack more than Skype, but I hate Slack with the passion of 1000 firey suns, especially in regard to many UIUX decisions. (Why does the new message line stay on the view AFTER I HAVE RESPONDED?) Not to mention the un...helpfulness (I guess) of their support.

Slack was great when it was new, because it was better in someway than everything else out there. Mind you not the same way for everything, but in some way it was better than most, if not all other options avaliable at the time.

That is not the case now. There are other options that are as good, or better. Slack MUST have been aiming for that 'fuck-you' size the entire time, because once they hit critical mass, they seemingly immediately stopped trying to be better, and started trying to be the one you were already paying; a serious downgrade in my opinion.

So coding in one language is a BIT of a red herring.

It only works if the paradigms your app uses are the same in the front and back. And I have nott seen a project where the KIND of problems that need solving (in the front vs back) were close enough for the same language to be a benefit.

I mean at the end of the day, I can build a house with JUST a screwdriver, but man, I'd rather use the right tool fot the specific job.

And at the end of the day, $LANG is a tool.

I don't see where it is canceled. The closest thing I see to canceled, is postponed.

From the update: 'We will not activate user level product usage tracking on GitLab.com or GitLab self-managed before we address the feedback and re-evaluate our plan.'

That leaves a lot of wiggle room.

To the extant that the local news knows anything, it is being reported here that the water will be returned to circulation (for lack of a better word) via the sewer, and its treatment cycle.

I have not used TS, but I have used Flow, which is just a typesystem for JS from Facebook.

I was never confident that the typing I was adding was doing anything other than making the Flow interpreter(for lack of a better word) happy. I had no more confidence in my code that with out it.

So I removed it.

I believe that well maintained linting rules, and good code reviews (you are doing code reviews, aren't you) give you all the same protection, and less false sense(s) of security.

Like you imply (I think), it is still just JS. I beleive you are better served by understanding that, and coding carfully.

I am genuinly curious; I promise I am not just trolling here...

Why is it important to call out the fact that is in [lang]?

This is the one I used.

Thanks for this, I will check that out.