conradk

How does Vue.js compiled templates compare to Glimmer ?

It may not be perfect for everyone, but in that case, no need to rage. You can just use any of the 38472647893242 different linters out there.

What I like about StandardJS is that I don't need yet another config file just for a linter. lintrc, babelrc, webpack.config.js, karma.config.js, etc, etc. Having one less thing for people to need to understand is a nice feature in and of itself IMO.

And I actually tended to disagree with some of the StandardJS choices before adopting it. After working with it for a few weeks, I realize it makes absolutely no difference. I just have a linter that works with no config.

That's not what I meant to say at all.

Here, I saw what looked like a new project. You say I should have understood right away because Glimmer is said to power Ember's components. But the Ember team could very well have built an entirely new engine for its components. I thought Ember used to use Handlebars (didn't it?) and had just recently built a new engine (aka Glimmer) instead of adapting an existing one (React, Vue, etc). But that sounded odd, hence my question.

If you see these sorts of things all the time, there may be a reason: communication is hard and we all interpret things a bit differently (depending on our experience, our mindset, our native language, etc).

Ah, thanks for explaining that ! I thought the Ember team had started an entirely new project instead of reusing something that already existed. If they extracted it, that makes much more sense to me now.

I can't help but think: yet another front-end library. But Ember being solid, there is probably good reason for this project.

What does Glimmer do that all of the existing view libraries couldn't do ? x-tags, vue, react, preact, etc, etc, etc.

Wouldn't an abstraction layer on top of any of those libraries have avoided the need to create an entirely new project ?

As a developer, the first thing I think when I see this is: am I going to be locked into a proprietary solution ? what happens when you suddenly increase your prices or your company goes down ?

What's the advantage of CloudRail vs something like Apache LibCloud ?

Oh, I thought "clipboard" was dual licensed to GPL and/or Apache 2.0. My bad. I hadn't seen that the x11 related code was purely GPL 2.0.

Thanks for your help, Steve !

Not sure why they rebuilt a clipboard library when "clipboard" exists (I think it might even be used within Servo, not sure): https://crates.io/crates/clipboard

I've been using Vue.js at work for this kind of thing: http://reassurez-moi.fr/taux-pret-immobilier

It was as simple as adding Vue.js itself and one JS file for custom code. I tried using Angular but right off the bat, I had to install hundreds of dependencies via NPM.

That's what I like about Vue.js. It's simple to reason about for the kind of use case I linked above.

Are you sure ? What are you basing this on ?

I thought Zapier was mostly business, and it's been running for a while now: https://zapier.com/

Can anyone comment on how rkt compares to Docker regarding the issues from this article ? And how does rkt compare to Docker in production in your experience ?

I've been using Docker in production for a single server website and have had very few issues. I do like how easy it is to reproduce a working environnement with a "docker build" though.

That being said, I think that just using Ansible on a server is probably an easier and more reliable solution. Ansible is battle tested and allows to have reproducible environments too.

I guess the reasoning would be that some hackers probably have found vulnerabilities they'd rather sell on the black market for 50K than sell to Facebook for 5K.

Thanks for the explanation !

How do app updates work with Sandstorm ? For example, if I host an instance of the Ghost blog. Now, say it updates from version 1.2 to version 2.0 (which means probably a breaking database schema change or something). How would Sandstorm go about updating it ?

Why is that ? I've never used Ember, but it seems like the framework with the best tooling and backwards compatibility track record. Maybe I'm wrong, I don't know.

Actually, Symfony has corporate backing with SensioLabs, if that's the company you are referring to, but Symfony is also largely developed by the developer community. You can submit patches, feature additions and they can be merged if there is a consensus on the quality and usefulness of the patch.

I think Laravel has the same development model.

I would choose Symfony. I believe it matches all of the above criteria.

And it has:

- amazingly simple upgrade paths, backwards compatibility guarantee on minor and patch releases

- regular, non BC breaking, updates and new features

- corporate backing

- large ecosystem of "bundles", which are Symfony's addon system

- cli tool for scaffolding, debugging and more

- strong conventions that help keep code structure clean when you are in a team of 2+ members

Why is avoiding negative side effects a wasteful proposition?

What's the difference between this and jQuery autocomplete (or similar things) ?

Just read about it being sha-1 (source: http://www.pcworld.com/article/257045/security/6-5m-linkedin...).

First commit for Redox was April 20th 2015. First commit for Redux (the JS library, if that's what you're talking about) was May 30th 2015.

Maybe we'll be able to take better care of the elderly. Or maybe we could spend more time educating children, with more teachers per class. Maybe we will have more time to teach people surfing. Maybe we will have more time to play cards, that may mean more need for coffee places to be open.

The list goes on and on.

Oh, now that's cool ! I see you've added a "help" command. And "cd REST-for-TYPO3-rest.cundd.net" makes a lot of sense now that I can see that "REST-for-TYPO3-rest.cundd.net" is a directory with the "ll" command.

I like it ! :)

Kudos on implementing this idea :)

It's a bit awkward, to be frank, though. When I type "ls RE<tab>", it autocompletes to "README" even though there is another file called "REST-for-TYPO3-rest.cundd.net".

So then I type in the full filename and I get "undefined":

> cat REST-for-TYPO3-rest.cundd.net

undefined

Maybe "cat <filename>" could open the URL in a window or something. It seems like the only possible thing at the moment is "ls", "pwd" and "cat README".

Everytime I read something about SemVer, breaking changes, etc, I can't help but think about how well Symfony (the PHP framework) handles this.

With Symfony, major version changes are not there to break things or bring in tons of new stuff. Instead, it just removes BC layers for stuff that has previously been working but deprecated (with appropriate deprecation warnings).

This makes it easy to switch to a new major version: simply fix all deprecated calls and upgrade, done. At least that's what I experienced moving a project from Symfony 2.x to Symfony 3.x.

The negativity in the background video is NOT good (ironic that I use a negative sentence to say that).

Other than that, it looks nice. What about if multiple customers write in at the same time though? Do they all speak into the Slack channel that you create? That seems like it would be confusing, having all customer discussion mixed together in one huge channel.

So? It's valid, isn't it? "I'm a teapot"?

Isn't MIT compatible with GPL though ? If it is, what's the point of having both ?

I would say it is particularly true for Symfony, but other package maintainers, like Tailor Otwell for the Laravel framework, do an impressive job at documenting how to upgrade to newer versions and keeping BC to a minimum.

For instance, I just recently upgraded from Symfony 2.7 to 2.8. The upgrade path was pretty much "Remove all deprecated warnings, upgrade your Symfony package, done". The same upgrade path is used from Symfony 2.8 to 3.0, which makes it really easy to upgrade.

Symfony, as most PHP dependencies, can be installed via the "composer" package manager, which is pretty much the only package manager that is used in the PHP community, it seems. As dchesterton says, it is a very good piece of software.

Feels good to see a JS lib last that long and still be actively maintained, deprecating obsolete features and adapting to the new ways we use our browsers without breaking BC (or else explaining how to migrate).

Coming from Symfony (PHP), this just feels right: keep moving but make it easy to follow along.