wycats

15 ms·

91.
by wycats 12y ago
I definitely can see why you'd see RC3 as a complete rewrite, but I don't understand why you'd feel that way about RC3. There were definitely changes, but they were much smaller and motivated by significant feedback by users
92.
by wycats 12y ago
I hope not!
93.
by wycats 12y ago
Thanks for the feedback. Personally, I feel like we nailed down the important changes earlier this month, and I agree that further churn at this point is likely to cause more harm than good. For what it's worth, the issues you linked t
94.
by wycats 12y ago
I'm really sorry that this was your experience. I give a little bit of historical context elsewhere on this thread[1]. [1]: https://news.ycombinator.com/item?id=9280602
95.
by wycats 12y ago
For people who have been dealing with the churn of JSON API, represented throughout this thread, I'm genuinely sorry. Let me try to give some perspective on the history. For a long time, JSON API was more of a set of guidelines than a
96.
by wycats 12y ago
> Since so many parts of the base specification are optional MAYs, and there is no prescribed mechanism for feature detection, there is no way to figure out if a server supports a particular feature of this spec without trying to do some
97.
by wycats 12y ago
I don't remember much of an objection to CoffeeScript on the grounds that it requires a compilation step. For example, here was my statement advising Discourse to avoid CoffeeScript in 2013: https://meta.discourse.org/t
98.
by wycats 12y ago
In what browser?
99.
by wycats 12y ago
I don't know of any TC39 member who thinks it's "good enough". It's my personal top-priority to leave Word behind as soon as ES6 is shipped.
100.
by wycats 12y ago
Yep. I shipped Tokaido and people use it. It was mentioned on Ruby Weekly last week. You can get releases at https://github.com/tokaido/tokaidoapp/releases . Andres (who now maintains the project) released Tokaido
101.
by wycats 12y ago
It's slow. Real slow. The original demo really stressed Ember's pathological cases, so it was a great thing to keep in mind as we developed Glimmer.
102.
by wycats 12y ago
Do you mean https://developers.google.com/web/fundamentals/input/form/us... ? If so, it has since become standards track: https://html.spec.whatwg.org/multipage/forms.html#dom-form-r
103.
by wycats 12y ago
They're very useful for infrequent (or first-time) travelers, but pointless for frequent travelers.
104.
by wycats 12y ago
As someone who has written many thousands of lines of production Rust code, this doesn't ring true to me at all. Ownership semantics have dramatically improved my ability to reason about my code, not the opposite.
105.
by wycats 12y ago
For what it's worth, I've written two fairly large pieces of code in Rust: Skylight and much of Cargo. In both cases, the amount of unsafe code was very small (tiny) and restricted to FFI boundaries, which are "unsafe" e
106.
by wycats 12y ago
> Did anyone ever really argue that we should abolish time zones in general? As I said in response to another thread, yes. People argue to abolish timezones. An example from Vox: http://www.vox.com/2014/8/5&#x2F
107.
by wycats 12y ago
Here is an article by a smart person on Vox arguing precisely for the abolishment of Time Zones: http://www.vox.com/2014/8/5/5970767/case-against-time-zones
108.
by wycats 12y ago
Exactly. His point is that people who argue for abolishing time zones are playing a classic shell game. They're talking up the benefits of the new system while ignoring its problems (and the benefits of the old system). This kind of sh
109.
by wycats 12y ago
Both of you guys missed the point. The problem that people are trying to solve by abolishing time zones is the annoying need to deal with time differences when scheduling meetings. The "I need to consult a table to schedule meetings&qu
110.
by wycats 12y ago
Once those steps are literally just "use iojs", I think the calculus is a little different, no?
111.
by wycats 12y ago
It looks like iojs is only going to ship features once they've shipped in Chrome without a flag. The compelling reason to use the features is that they're useful! EDIT: I don't think anyone is going to be sympathetic to holdi
112.
by wycats 12y ago
Important to note: because JavaScript itself is always backwards-compatible (1JS), any code that runs on Node will run on iojs, but not necessarily vice versa. That means there need not be a split in the ecosystem: people who want maximal
113.
by wycats 12y ago
Yes, but the cost is that those gems have to worry about supporting a lot of different versions of Ruby. Writing a fix for Net::HTTP only involves making it work on master ;)
114.
by wycats 12y ago
For what it's worth, while a lot of people complain about the Ruby standard library, when I want to reach for an HTTP library that is properly threadsafe, properly supports encodings (and in general is properly integrated with whateve
115.
by wycats 12y ago
Citation: http://support.microsoft.com/kb/170559
116.
by wycats 12y ago
The primary difference between Ruby and Python, from where I'm sitting, is that Ruby's change was purely at the API level, so it was feature-detectable and shimmable by libraries like Rails. I talk elsewhere in this thread about t
117.
by wycats 12y ago
I agree with the vast majority of what you've said. One thing worth noting is that there was a TREMENDOUS effort that I headed up in the Rails 3 era to very aggressively attempt to reduce the number of encoding-related problems in Rail
118.
by wycats 12y ago
Momentarily, and Matz appeared to feel so bad about it that they have been far more aggressive about tiny-version changes ever since.
119.
by wycats 12y ago
Han unification is one problem; another problem is that not all encodings can be round-tripped losslessly through Unicode. Shift-JIS, for example, has multiple separate characters that convert into the same character in Unicode, and therefo
120.
by wycats 12y ago
> As for dynamic dispatch...does Rust not support it, or is there some language construct that allows solving the problems dynamic dispatch solves without imposing annoying limitations or needless verbosity? Rust supports dynamic dispatc

More ›