olingern

Like others have mentioned, it seems that elm has done a great job of promoting itself, but lacks the structure to make big changes.

It screams of needing some sort of governance and RFC process ( edit: seems that there is an RFC process [1]) so that all parties could make their case.

The Angular 1 -> 2 transition should be a lesson to most that if you leave your users hanging, they'll go find another ecosystem.

[1] - https://groups.google.com/forum/#!forum/elm-dev

Late to the party, but can't wait for the technical write up on this.

I think npm has been a headache for everyone at some point, which is one of the main reasons I started contributing to Yarn. I think npm has done a lot of good work in the past year to respond to the necessary change, so kudos to them for their work; however, it's nowhere near the rock-solid package manager that we need. If the Javascript ecosystem is to ever be taken seriously, and not as a toy -- it has to have more reliability.

Ergonomically, I currently thing it's ahead of many other package managers because of how simple it is to get running. The number of "gotcha's" after npm install is nothing to shake a stick at, though.

One of the things you can do to get builds that aren't as suspect to npm registry issues is configuring an offline mirror [1].

From the post:

"Repeatable and reliable builds for large JavaScript projects are vital. If your builds depend on dependencies being downloaded from network, this build system is neither repeatable nor reliable.

One of the main advantages of Yarn is that it can install node_modules from files located in file system. We call it “Offline Mirror” because it mirrors the files downloaded from registry during the first build and stores them locally for future builds."

1 - https://yarnpkg.com/blog/2016/11/24/offline-mirror/

It's still in development. I didn't think anyone would be interested, since I see one pop up on /r/learnjapanese each month.

Perhaps, I'll clean it up and submit my first ShowHN

Trello is what came to mind at first. It made more sense to buy it, rather than it being competition to Jira.

Hipchat could have easily taken the space that Slack exists in. Lack of product vision and resources dedicated to the project ultimately led a non-existent competitor to own the entire market.

> If you are a Java (or Kotlin, or Scala) developer who used to write back-end code, TeaVM might be your choice. It’s true that a good developer (including Java developer) can learn JavaScript. However, to become an expert you have to spend reasonable amount of your time.

Oh, this is nice. I finally have a reason to give Kotlin a go. I have some time off and want to write something basic. Pretty excited about this, Rust, and all things wasm popping up.

I am, in no way, excited about debugging it, though.

I may give Ubuntu a go again. Having a dual boot system was nice in the past, but I also found myself needing one thing that justified using Windows more. In high school it was Warcraft 3, in college it was powerpoint, Visual C++, plus others.

Now that I don't game as much and get to choose the software I use, Ubuntu might work out.

I do enjoy Apples approach to system UI, though. Windows and Ubuntu have always "made sense" where as OSX makes sense and feels nice. Something weirdly intangible that I didn't understand until I was an OSX user.

The current releases within the Apple ecosystem are rough. Currently weening myself off of iMessage to reduce the pain of potentially moving outside of the OSX ecosystem.

Apple is basically handing Microsoft a golden ticket. With Windows looking pretty dev friendly these days, there's finally some competition for an OS that's both UI and dev friendly.

Tokyo and some other links are broken on job listings page [1]

[1] - https://www.facebook.com/careers/jobs/a0I1200000LSsTmEAL

Agreed on corporate interests, but I'm not sure about keeping government jobs weak.

With the government, your target market is every citizen (plus visitors, immigrants, etc.). The private sector has to create its market by providing a product or service, whereas the government is obligated to provide some products and services.

What incentive is there for government to squander talent and keep itself workforce weak?

I've cruised by it a couple of times, but my workplace is already bought in on AWS. Code Commit has some nice integrations for CI / CD whereas I can't really make the case for Gitlab other than, "I like it more"

Positioning it more like:

- It will save us X amount of time on average

- Give us better security through IAM

- Reduces fragmentation across org software

sells a lot better to people with credit cards than, "I like it more"

As an unhappy Bitbucket user, I have my fingers crossed for better Github enterprise pricing (does not scale for dev agencies with many repos), but mostly for AWS Code Commit.

It's somewhat scary the breadth that AWS has in their ecosystem now; however, Bitbucket is wrought with issues like:

- no large file collapsing, i.e. lock files

- random downtimes ( I wonder if they actually meet their SLA )

- feature requests on boards where Atlassian members ask why x is needed, followed by a slew of +1's, to only see someone ask 3 years later, "where is this at?"

I'm a jaded Atlassian user who believes they buy competition and then stagnant the product's evolution.

The other side of this is the stability that a government job provides to low to middle income classes.

The southern states where I grew up and went to college both lauded people who were able to secure government jobs. No matter how grueling or toxic a work environment becomes and no matter how inefficient workers become -- everyone stays in those jobs for the pension.

In cities and areas where education in literacy is higher it's as if the market "pushes" that desire out, and the perception around having a government job is largely negative (excluding contractors).

I wish there were a way to increase competition for gov jobs and change the perception of them without resorting to privatization.

> I've never found a place where it was easy to make friends, though the easiest has seemed to be language class full of other immigrants. We all had that one thing in common.

Learning and/or shared discomfort has seemed to foster the closest relationships I've had to date. Perhaps, it's time for more classes.

Coming from the countryside, it's such a strange paradox -- to be surrounded by so many people, but alone at the same time.

Health

- Undo minor case of hip impingement ( sitting down too much! )

- Connect with more people / foster better relationships. Who knew making friends in a city could be so hard?

Programming

- Finish SICP. Made it through four chapters with co-workers, and then everyone dropped off.

- Continue exploring functional programming

- Finish my homegrown Japanese kana / kanji language learning tool

Other:

- Take some of the wisdom from this thread[1], and make myself more "marketable" through blogging, giving talks, etc.

- Pass the JLPT 3 test

[1] - https://news.ycombinator.com/item?id=15994410

> I think you're projecting your own concerns onto the author

It's entirely possible.

> which is why the French approach is stupid

I think there's some merit to what they do, but it is a bit much.

> I do agree with him however that as Brits (and as Canadians in my case) we are losing something valuable by adopting American English unthinkingly and it's worth paying a bit more attention to individually when we use language as a result.

I would agree, but would say the author / BBC could have had more tact and not used the headline, "How Americanisms Are Killing the English Language." If a Japanese news outlet ran an article, "How the British have 'watered' tea down for more than 100 years" -- not too many Brits would be excited about reading it.

I think what he fails to understand, and many British for that matter, is that the language is not "owned" by anyone. Australians have probably augmented English more than us Americans, but I don't hear or see much complaining about their use of the language. The article comes off as whiny and unsubstantiated.

It's a tough time to be an American, and most people realize that. Exploiting that with bad journalism is just throwing gas onto a trash fire IMO.

edit: More importantly, if Brits want to preserve the language as they see it in their country, they should consider going the French route [1].

[1] - https://en.wikipedia.org/wiki/Acad%C3%A9mie_fran%C3%A7aise

No doubt we "Americans" have changed the language, for better or worse, but this comment is more about journalism.

I expect more from the BBC than to let a former Bloomberg journalist make generalizations without anything to back it up. "Awesome" occurring more often than "marvelous" doesn't provide us with anything other than the fact that the author appreciates the latter more than the former.

Seems appropriate that I should go write a piece for the BBC on how journalism has declined and how Brits are contributing, and be sure to cite this article.

Sitting in a cafe in Shibuya, Tokyo ( at the moment ), I would say there's a "oneness" to everything they do. Inconveniencing others is the height of moral crimes you can do here ( see your family being fined for your suicide [1] ). I think this permeates their culture to the point where they're more efficient so that they do not affect others, i.e. how on time trains are in Japan [2]. Of course, this is speculative, but it certainly does not feel like a, "I'll get mine, before you get yours culture" here.

[1] - https://www.irishtimes.com/news/health/families-fined-for-su...

[2] - http://www.bbc.com/news/world-asia-42009839

I feel like the US will continue to fall behind the curve until it's one day too late to be looked at as what other countries aspire to.

Oh, wait. No one aspires to be us anymore.

Japan also has a much different outlook on blue collar jobs, and (from studying the culture and spending ~3 months there) people seem to take genuine pride in their job regardless of what it is.

Contrast that with the MTA subway workers I see regularly huddled into groups, shooting the breeze and playing on their phones -- it's a widely different outlook on work.

Also regarding you [2] link, I can't remember where I read it, but I believe that operation took years of planning.

While I agree that NYC is much safer than when I first moved there five years ago -- threats still pose themselves from time to time (as anywhere will).

For example, I fell asleep for the first time on a 2 train last month, and was robbed. It was one of those, "Ah, this is definitely on me," moments. Easily preventable; however, it's still crime, nonetheless. Most importantly, I didn't report this (as many others in similar situations will not), so the statistics are probably not as accurate as headlines would like you to think.

I think this thread [1] along with unstable modules were convincing enough for people not to trust their production applications with an open source project that has a shaky future.

Most people who were interested in the approach moved their efforts to TrailsJS [2]

[1] - https://github.com/balderdashy/sails/issues/3429

[2] - https://trailsjs.io

> Generally, the cost of buying and running one server in a datacenter and staffing the ops team needed to keep the hardware running is cheaper than paying for a 24/7 server of comparable specs in the cloud

I would disagree here. You can run the metrics for your stack, but it's likely cheaper on AWS. https://awstcocalculator.com/

If you don't need to compute something but twice a day, or just certain times -- you can pay pennies on the dollar for a serverless function. There's no need for an entire server for things like this.

There is so much more overhead with bare metal.

There's an entire other side of building a web server that devs, thankfully, never have to see. OpenCompute [1] aims to standardize what that process looks like. To think that you can run bare metal, and do better than industry standards is naive IMO.

In the end, if you're worrying more about anything than business logic, you're not really delivering value -- you're solving engineering problems. You can sacrifice that control and solving problems for greater abstractions, i.e. serverless, fargate, etc.

Unless you have some extreme security requirements (which most don't) you probably don't have a good reason to run bare metal.

[1] - http://www.opencompute.org/

It looks like there is a lot of legacy code hanging out in the compiler [1], i.e. prefer module over namespaces.

[1] - https://github.com/Microsoft/TypeScript/blob/master/src/comp...

It's also strange to me why they inline their interfaces, rather than organizing them in a common folder / module.

I think there's the right tool for the right job, and that differs from person to person. Not every application needs an elegant concurrency model, and not every developer is ready to burdened with pointer management.

I think this is why Rails still exists, even after all the bad press it received after Twitter moved away from it [1].

Node is a great stepping stone for newer developers to get exposure to software development without having to learn a complex framework, .NET for example. It's an incredibly flexible language where you can embrace functional or object oriented programming.

Javascript can be a quagmire of a language at times, but once you learn to properly wield it -- it becomes somewhat endearing. A butter knife that will easily cut a steak, if you will.

[1] - https://blog.twitter.com/engineering/en_us/a/2011/twitter-se...

Lots of respect for Ryan. His ideas brought about major changes (for the better IMO) in both front-end and backend development.

It's hard to imagine a world without all of the tooling and frameworks that Node has brought about, even if has added an extra layer of complexity -- i.e. webpack.

So, by flying on an airplane I forfeit my privacy in exchange for a facade of security?

Nothing suspect about this.

As a person who would love more freelancing opportunities, the market is littered with sketchy proposals, undercut / underpaid projects, and just a bad experience.

Software Engineering Daily had a episode[1] on Gigster that seems to be trying to solve this, but I have no experience with that. They also tout only hiring "1% of all developers who apply," which doesn't really solve the other 99% of freelancer's problems.

[1] https://softwareengineeringdaily.com/2017/10/13/gigster-with...

Any advice you would give to a team going this route?

And, I've found that integration tests help keep my sanity if a refactor occurs anywhere. Any learning(s) for adapting to refactors across services?