matmo

Awesome, I'm glad to hear that. I still use the current mobile app despite my criticisms, but I'm definitely looking forward to the new one(s)!

That is definitely a plus, but the mobile app(s) for mattermost are pretty bad.

I'm guessing it was built a long time ago on cordova or one of those other "write once, run everywhere" frameworks where they just run everything in a WebView.

I think I read briefly somewhere that Microsoft already stores foreign emails in foreign data-centers in order to comply with foreign laws better since they target enterprise customers that have those types of absolute requirements. I guess Google might be having their foreign emails pass through US servers at some point?

I'm sure someone else has more detailed/informed answer.

>Gulp, Grunt, WebPack... What are we doing

Once you've accepted that JS is here to stay in browser-land (for now, at least), what alternatives are there for build tools?

As a younger dev, when I look at makefiles, I see the same level of complexity and "confusing-ness" that I encountered when I first learned about gulp or webpack configs. I keep reading posts like this on HN where people yearn for simpler days, but weren't the demands of websites and user interfaces simpler back then as well?

I've only been doing professional web development specifically for 4 years or so, so I don't have the same experiences of building in older technologies, but I simply can't imagine trying to build a large, immersive SPA without a modern framework. How do you manage global state or services? Just throw everything in the global namespace? How do you minify your js/css/html? How do you treeshake your unused code? How do you create a local proxied server to avoid CORS issues while developing? How do you autoprefix your css automatically? How do you develop with live-reload functionality? I know all of these can be done individually without these tools, but you can do these all individually without gulp/webpack/etc just by using node/npm scripts. These tools just package them into a more convenient format for common use cases, and tie complimenting tools together. It seems to me that everything would need to be custom built, and you would need to recreate complex scripts from scratch for every new project.

These tools obviously aren't perfect, but I'm not sure they're as bad as you're making them out to be either. Like I said, I don't have the same long-term experience as you or others might, so forgive me if I'm just being naive here.

Ok yeah, I suppose I haven't really pushed Slack to that limit either. Only using a team or two myself.

>My current main work laptop (a pre-TouchBar generation MBP) can only barely run a "heavy" JS-application like Slack and something like IntelliJ at the same time.

Is this hyperbole? I run both of these with IntelliJ memory settings maxed out on a MPB no problem. Granted, I have 16GB of memory, so understandably YMMV.

I see. Yeah, Angular probably doesn't target environments where it isn't the main/driving DOM/context.

How are you going to embed an app in another app/DOM without using an iframe, and how is creating that iframe going to be any harder to accomplish depending on the technologies used inside of it?

I'm not sure what you mean about components...Angular is component based. Are you referring to native web components?

Only some of these are percieved advantages over Angular. Alot of them are advantages over AngularJS, meaning AngularJS 1.x

I'm obviously biased, but using Angular (2+) with typescript and ngrx (observable based redux, essentialy) has been really nice to develop with.

IntelliJ for everything. My only complaint is that when I'm writing front end code, it has to do do more guesswork for the autocomplete suggestions, which takes more time, so I have to purposely stop typing for a second to let it find the suggestion I want so I can select it.

The worst part for me was going from being a "rockstar developer" on the team to having to explain why I suddenly can't meet the overly ambitious deadlines handed down from above due to anxiety, depression, panic attacks and extreme insomnia.

>In the absence of evidence, invention and speculation don't really help

In the same vein, until I see actual evidence (and not just "Mr. SoAndSo said so-and-so is true), I'll factor in the claims of the US government and media as just hypotheses.

I think its unfair to say that we should refrain from discussing or theorizing about topics when the truth is murky just because we can't test it. I'd test it if I could, but the reality is that we're never going to have that ability (unless we magically achieve complete governmental transparency somehow).

Almost seems like an attempt to shift the dialogue from "Republican vs. Democrat" to "USA vs. Russia". Why put out this article now, instead of when this first became public "knowledge"? I get the feeling this is the democratic establishment trying to say "Look, the GOP is getting hacked too! Lets all turn our focus on Russia!"

This is admittedly speculation, though. You can't really trust the government or the media these days, so I don't even know which bits of information I'm working with are true or false.

Doesn't babel (ES6 --> ES5) solve this issue or is there more to it?

I think the two main solutions are pipes and shared memory.

Better title: 6 generic questions answered by someone who should be answering much more pressing questions

What is OData? The website does a poor job of explaining it from a high level. The only discernible feature I see is adding "functions" to url's (ex: http://services.odata.org/V4/TripPinServiceRW/People("russel...)

I've seen "OData" mentioned here and there, but I've never understood the difference between OData and a classic REST API.

Can you override the autogenerated setters and getters in Kotlin?