Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
wycats
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
16 ms
·
121.
▲
by
wycats
12y ago
A design goal of Rust is to target the performance of well-written, safe C++. It doesn't (today) even ship with a garbage collector, discourages heap allocation (which is your only option in normal Go), and avoids dynamic dispatch in t
122.
▲
by
wycats
12y ago
> Does this affect the ability to distribute your frontend over a CDN? Is this common practice for current Ember applications? It is a common practice and it doesn't affect distribution over a CDN; it makes the CDN story stronger im
123.
▲
by
wycats
12y ago
> How does transparent server-side rendering of Ember change the role of what was the server-side app before? Are you now managing a separate server environment for your Node Ember application? Our goal is not to make Ember an "isom
124.
▲
by
wycats
12y ago
As someone who wrote a lot of code not in the standard library, I championed this RFC pretty heavily. Part of the reason is that I noticed that with the lifetime elision rules, code using abstractions (as opposed to the implementation o
125.
▲
by
wycats
12y ago
I would be very surprised if something like C# and ES7's `async/await` syntax doesn't land in Rust after 1.0.
126.
▲
by
wycats
12y ago
I think the best I can do here is my usual answer: take some time every week to work on a problem that is a little bit harder than what you already know how to do. It requires discipline, and it's hard, but it reliably results in level
127.
▲
by
wycats
12y ago
I did my first real coding in around 2005, and quickly got interested in both jQuery and Rails. Really good timing in retrospect!
128.
▲
by
wycats
12y ago
Idiomatic, typical Rust code does not involve a garbage collector, which makes it suitable for embedding in environments with a garbage collector as well as any application with real-time (no pauses) requirements.
129.
▲
by
wycats
12y ago
To be blunt, I would not have picked Ember, Handlebars, TAG or TC39 due to their "hype factor". In the cases of TAG and TC39, I saw an opportunity to take low-hype, low-bandwagon organizations and revitalize their missions and pur
130.
▲
by
wycats
12y ago
One of the nice things about Rust is that it provides a lot of high-level abstraction capability in a way that doesn't impose any cost on the abstraction. This means that, in theory, one could make a pretty good web framework in Rust t
131.
▲
by
wycats
12y ago
Most definitely not. Ember (and its ecosystem) and Rust are the two open source projects that are currently consuming most of my time. I have easily spent as much time on the planning for Ember 2.0, HTMLBars, and Service Side Rendering as I
132.
▲
by
wycats
12y ago
I replied to this a bit on the other HN thread on this topic: https://news.ycombinator.com/item?id=8741987 TL;DR embedding small libraries with high-performance or low-memory requirements into programs written in high-level
133.
▲
by
wycats
12y ago
For what it's worth, a big part of this is slowly winding down earlier commitments over time. I joined TAG a couple years ago, and decided not to run again this year because I had largely achieved my original goals of changing the comp
134.
▲
Yehuda Katz and Steve Klabnik Are Joining the Rust Core Team
(blog.rust-lang.org)
423 points
by
wycats
12y ago
|
131 comments
135.
▲
by
wycats
12y ago
Google deserves every last inch of this.
136.
▲
by
wycats
12y ago
Another Skylight founder here. Focusing on Rails lets us build a really awesome end-to-end solution that works out of the box. Building an intuitive, explorable interface means constantly considering the application's context, and I ca
137.
▲
by
wycats
12y ago
For what it's worth, I've been using Rust for over a year in my product ( http://skylight.io ) and it matched my needs pretty closely. Our product is a performance monitoring tool that runs inside of Rails apps, so it&#x
138.
▲
by
wycats
12y ago
Matz worked on a spec for the Ruby language, which is now an ISO standard: http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_...
139.
▲
by
wycats
12y ago
As a person who has spent weeks of my life trying to persuade AppCache + HTTP caches to do what I want (and who subsequently became a champion for the low-level primitives that became SW), I just don't agree with this. It seems true in
140.
▲
by
wycats
12y ago
Unfortunately, HTTP caches have opaque, browser-provided semantics that work sometimes and mysteriously don't work in other cases. They can't be used to ensure that you have a complete atomic set of application assets, are often p
141.
▲
by
wycats
12y ago
> The only real quirk I see here is the fact that strict mode isn't enabled by default (or better yet not even an option to turn off) but that is because it would kill backwards compatibility Worth noting: modules in ES6 are "s
142.
▲
by
wycats
12y ago
I once wrote a description of `this` from the perspective of `call` as a "primitive": http://yehudakatz.com/2011/08/11/understanding-javascript-fu... It seemed relevant. :)
143.
▲
by
wycats
12y ago
The last time I talked on Hacker News about Ember was in the comments about Ember 2.0. Before that: months ago. Most of my recent comments have actually been about Rust, not JavaScript at all!
144.
▲
by
wycats
12y ago
This is actually more than just web components. iOS and Android have shared application architecture, tools, and navigation between screens. On the web, we'll never have "one true" solution to these problems, but the animosit
145.
▲
by
wycats
12y ago
I completely agree with this post that there is churn fatigue. Part of that is in libraries, but an even bigger part of it is in the tooling that people use to build JavaScript applications. It's easy to see all of these new things fly
146.
▲
by
wycats
12y ago
So for what it's worth, this blog post is mostly a technical deep dive for people who are very interested in the full details. From a UI perspective, I (and many others, including core team member Aaron Turon) have argued successfully
147.
▲
by
wycats
12y ago
It's worth noting that the very next release (1.9) is already locked and loaded (it branched to beta). So when Tom says "next release" he means 1.10. Also, some of the points in the RFC are features that depend on the new t
148.
▲
by
wycats
12y ago
Yes, we do exactly this at Tilde and it works well. This sounds like a good blog post and possibly some released code that people can use. Because the division of labor with Ember CLI is relatively clear, I expect build tool ecosystems to b
149.
▲
by
wycats
12y ago
Indeed. Here's a physical comparison: http://www.phonearena.com/phones/size#/phones/size/Apple-iPh... Using screen-size as a measure of physical size let Apple pull off a pretty epic PR coup. The iP
150.
▲
by
wycats
12y ago
And I expect virtually all of the methods on slice to be available on String before long. I think it's a bug that this isn't the case today. It's already possible to have a function take "either a String or slice" g
More ›