wycats

23 ms·

181.
by wycats 12y ago
I'm objecting to saying "we have reached 1.0" when what they really mean is "we are releasing 1.0 beta 1"
182.
by wycats 12y ago
"You’ll notice we’re using the word “GM”, not “final”. That’s because Swift will continue to advance with new features, improved performance, and refined syntax" Typically, when people say that a language "reached 1.0",
183.
by wycats 12y ago
I don't believe this is the traditional definition of "reached 1.0".
184.
by wycats 12y ago
> If you had several candidates of equal ability, would you still use an exploding offer? 1) yes 2) I don't think I've ever been in a situation where I had multiple candidates without any preference.
185.
by wycats 12y ago
Whenever I've offered an exploding offer in the past, it's because I had several candidates: an extremely strong candidate and several strong but somewhat weaker candidates. In general, all of the candidates have a limited timefra
186.
by wycats 12y ago
I slightly disagree with @machty. I agree that most of the reasons people give for hating on JSX are somewhat off the mark. HOWEVER: the fact that JSX is XML and not HTML syntax is a real issue. `<label for="foo">` doesn&#x2
187.
by wycats 12y ago
I personally haven't had much trouble with: npm install foo --save-dev When you go beyond a single developer playing around, having a quick, well-known place to look to learn what dependencies are being used is very useful.
188.
by wycats 12y ago
Ah. I would probably clarify the language to make it clear that having a manifest approach is the intended approach for real-world apps, but that it can be left out when playing around.
189.
by wycats 12y ago
It sounds like this means that if I wanted to use a specific version of Ember, I would have something like the following line in many files: require("emberjs/ember-component@^1.6.1") Doesn't this mean that to upda
190.
by wycats 12y ago
Node?
191.
by wycats 12y ago
How would you say that Cabal is horribly broken?
192.
by wycats 12y ago
O_o
193.
by wycats 12y ago
The goal is to use package manager defaults and community pressure to keep things on the straight and narrow. We'll see how it goes!
194.
by wycats 12y ago
> FWIW, I said it and did it. Same.
195.
by wycats 12y ago
> Getting out of the way of Silicon Valley and ensuring a strong safety net add up to a political paradox. Because Silicon Valley doesn’t want to pay for the safety net. > There is very little evidence that the people who are getting
196.
by wycats 13y ago
And Ruby, and Rust. It's close to universal.
197.
by wycats 13y ago
It's worth noting that the XSS vulnerability ("A user could inject scripts into the npm website via the README and license fields") assuredly exposed a whole slew of easy-to-exploit vulnerabilities, and the community should f
198.
by wycats 13y ago
I think what they're trying to say is that the bug is exactly as bad as the Rubygems incident, but they got lucky and it wasn't exploited.
199.
by wycats 13y ago
A package manager will be a forcing function for stability. The Rust team wants to ship Rust 1.0 sometime late this year (I think? Correct me if I'm wrong) Building a package manager is not a one-month project, and getting it done in p
200.
by wycats 13y ago
I have included my phone number on virtually every piece of public email (to mailing lists) I have ever written. I have found that people do not abuse it.
201.
by wycats 13y ago
@molecule Fair question. Tokaido ended up taking far longer than I expected (a big, huge mea culpa for sure). TL;DR: At long last, I plan to ship Tokaido, along with a website, documentation and automation at RailsConf this year. That would
202.
by wycats 13y ago
You can use CSS flexbox too :)
203.
by wycats 13y ago
I hate to agree with this troll, but I don't see how to disagree :(
204.
by wycats 13y ago
We said this in the early days of Ember. Specifically, that while we were still making a lot of changes to Ember before 1.0, that we were going to go to strict SemVer compatibility post-1.0. This made it clear to early adopters that things
205.
by wycats 13y ago
1.8 to 1.9 was a HUGE release in terms of breaking changes. Probably the most notable change was the introduction of proper unicode support. Unlike Python, which changed syntax at the same time, Ruby tried to maintain compatibility with exi
206.
by wycats 13y ago
Yep! Those differences are totally correct. There are tradeoffs in each approach. One of the benefits of the Rust approach is that you can have a different implementation for each type (polymorphism), which is a feature I needed last week i
207.
by wycats 13y ago
This must be a question of aesthetics because the 2.days().from_now() seems perfectly obvious to me. Maybe someone can help me understand why it seems confusing?
208.
by wycats 13y ago
That's essentially how traits work in Rust. You need to import the trait into your scope, and 2.days().from_now() is essentially sugar for days(2).from_now() where days() returns a TimeChange object.
209.
by wycats 13y ago
In Rust, you have to import a trait (in this case active_support::Period) into the file that uses 2.days(). It's not a global change. If you see 2.days(), you know where to look for the definition, and the type system means that you ca
210.
by wycats 13y ago
I wrote the original implementation. One thing worth noting is that the implementation isn't globally extending `uint` with `.days()`. In order to write `2.days()`, you need to first import the trait that provides the implementation. F

More ›