you know about swc right? https://swc.rs/

Yes, but a bunch of the Typescript support is closed sourced . No idea, if that's important for you.

Type checker, yes. I don't think esbuild comes with a built-in typechecker either.

Is there anything else I am missing?

I was referring to swc

It's important to me. Could you please link me to where these nonfree bits are?

omg lol

I'd recommend esbuild over SWC. It's much more mature.

Glad it is GA now, but it is still has some issues:

* If i use non core parameter in pipeline, BO ask me to move to classic interface

* If i do not use Github like pipeline, interface become partially useless. It means empty branches, empty PR columns etc. Where is good old custom pipelines?

But anyway it is good move forward!

PS: pipelines itself also has some issues, like really small number of useful steps, literally only sh step used everytime. Also in case of custom pipeline it is still unclear how to abort build in code. And using groovy collections methods is veyr inconvinient (like trying to use .collect to create command like options for next sh step)

> using groovy collections methods is veyr inconvinient

It looks like Blue Ocean generates Apache Groovy DSL code for the pipeline. From their pipeline doco [1]: _In order to provide durability, which means that running Pipelines can survive a restart of the Jenkins master, Scripted Pipeline must serialize data back to the master. Due to this design requirement, some Groovy idioms such as collection.each { item -> /* perform operation */ } are not fully supported_

I wonder how feasible it is to make any edits at all to the DSL and have the new code read in successfully by the Blue Ocean UX. Perhaps the collections methods aren't the only restrictions.

[1] https://jenkins.io/doc/book/pipeline/syntax/#differences-fro...

Strange to see you are looking for remotes, if you become unresponsive as soon i want to want remote.

Yes, but it breaks some cases. I'd recommend to wait 5.7.1 (https://github.com/nodejs/node/issues/5400)

Probably an ignorant question but this makes me wonder: how can they release when their tests don't pass?

I haven't been following, but it looks like the tests were passing and they just didn't have tests to prevent these issues that came up.

Break early, break often :-).

This is exactly why I've stayed away from this stack wherever possible!

I hope you stay away from GCC as well, which for example broke C++ in 4.7.0 and fixed it in 4.7.2.

Any new major release is bound to break something for someone. Prudence suggests adopting a major release only after a few months. This applies to all platforms.

You're right; I was a bit harsh. I'm just really conservative platform-wise - Node is just starting to get there.

The Node/npm ecosystem does still feel a bit wobbly as an application platform, though, kind of like Ruby was five years ago...

This is not true. Some platforms, such as Clojure, are usually very stable once released, and there is rarely the need for point releases, as the code was stabilized during the alpha/rc periods.

We do similar thing but with workflow plugins.

Finally! It was very disappointing that girl that smile and had good relationships with out senior manager had the same salary as me, even if i got the best score in our delivery center.

Doesn't equal pay legislation mean that in practise if you got a pay rise, assuming you're male, that any female doing what might appear in court to be the same job has to get the same pay rise??

IANAL, but I think that's what's sticky about equal pay, or one thing.

For a given job, not all _people_ will get the same pay, and as individuals, a particular man and a particular woman may not make the same, but across an organization we should find some balance, there should be women who make more than some men, etc..

I don't think anyone wants a situation where granting any individual a raise means that everyone with similar responsibilities (no two people 'do the same job') gets the same raise.

But as I type this, it's clear how all of this grey area can (and surely IS) be leaned upon to maintain the status quo.

If the company does a good job codfying your contribution in a role+level, there is no problem giving everyone in the same role+level the same pay.

> but really why not convenrt them to string represntation and put to simple object?

Because as soon as you might have "toString" or "__proto__" as a key things go all haywire.

Why do all these strange workarounds?

We fixed this with installing npm proxy mirror. So each install happen from this proxy and if something missing it will be downloaded and saved for later from central.

In this case we always have the same dependencies that we have locally. But of cause this means you need own box with proxy.

(in our case it is nexus)

Looks interesting, will give it a try. Also nice project is https://stackedit.io/.

There is no brew formula?

For rust? There is...cargo not so much

aroch:~/staging/|⇒ brew info rust

rust: stable 0.10 (bottled), HEAD

http://www.rust-lang.org/

/usr/local/Cellar/rust/0.10 (74 files, 174M) *

  Poured from bottle

From: https://github.com/Homebrew/homebrew/commits/master/Library/...

aroch:~/staging/|⇒ brew info cargo

Error: No available formula for cargo

Rust has a brew package. Cargo is new so it may be a day or three before it gets out there too.

Hmm, well, rust's brew seems a little outdated (0.10), so if you are intent on using Cargo soon, I would recommend on building rust yourself or grabbing a new binary from their website.

There is a homebrew-cask of Rust's nightly binary. I think this should work:

  brew tap caskroom/cask
  brew install brew-cask
  brew tap caskroom/versions
  brew cask install rust-nightly

Stuff being either in Cask or Homebrew is just terrible. Homebrew also has a versions tap. Those two projects should combine efforts and remove ambiguity.

I 100% agree with you. It took me like an hour to figure out where I thought it made sense to put rust-nightly, and I'm still not really sure I did it right. But it works and is way better than the morning compilation cronjob I used to use.

I agree, it works, but we need to keep pressing those guys... or contribute. Cask still doesn't have reinstall/upgrade. As far as I know, Homebrew can't upgrade packages with head versions, and, worst pain of all - Homebrew doesn't support Yosemite or any unreleased OS X version. Being a tool for developers primarily, all the above are must-haves!