wycats

37 ms·

1.
by wycats 5mo ago
As one of the original authors of Cargo, I agree. lockfiles are for apps and CLIs are apps. QED.
2.
by wycats 4y ago
Certainly!
3.
by wycats 4y ago
A little more context: I've been working on the design of this reactivity system in some form since roughly 2018 as part of the Ember framework. The original design of the reactivity system made its way into Ember Octane as the "a
4.
by wycats 4y ago
Hey! Owner of the original repo here :) Like @tomdale, I'm surprised to see this on the front page of Hacker News! I have been working on more detailed documentation about the overall model. It's also still in flux (and not ready
5.
by wycats 7y ago
You're absolutely right. We took a lot of inspiration from the MobX API design. One thing worth calling out: MobX requires you to mark getters as `@computed`: class OrderLine { @observable price = 0 @observable amount =
6.
by wycats 7y ago
And on top of that, the fact that we use a simple reactivity primitive under the hood[1][2] means that we have been able to transition from an API designed for 2012-era two-way bindings to a unidirectional data-flow model with minimal disru
7.
by wycats 7y ago
I think that's probably a good change to the default. Today, `ember build` is analogous to `ember s`, and most people deploy to production with `ember-cli-deploy`. But that's not a good enough reason :) Thanks for surfacing this!
8.
by wycats 7y ago
You got that right. We got a lot of inspiration from the React ecosystem, both in terms of component design (the root element is just another element) and composition. Those changes played out differently in the context of Ember, because of
9.
by wycats 7y ago
You're not alone! The Ember core team broadly agrees with this goal. With Octane, we focused on landing broad ergonomic improvements in a compatible release of Ember. At the same time, we've been working on updating the way that E
10.
Ember.js Octane Edition(blog.emberjs.com)
187 points by wycats 7y ago|75 comments
11.
by wycats 7y ago
Ultimately, the value prop of a tool like Graphiti or GraphQL is independent of the exact details of the wire format. Graphiti uses JSON:API[1] under the hood as its protocol, which is a language-independent protocol with a wide variety of
12.
by wycats 7y ago
> It doesn't appear to solve some or the 2 major headaches graphQL is great at solving: * clients choosing how much data they need. On a desktop on broadband client, I want details of a list of entities, while on a mobile app with l
13.
by wycats 9y ago
I split my time between Ruby, JavaScript (mostly with TypeScript) and Rust, with occasional Java and devops work. Of those, JavaScript (with TypeScript) is my predominant language at the moment, but the mix changes pretty often. Skylight&#x
14.
by wycats 9y ago
The short answer is no. We work differently than other similar products, in that we rely heavily on aggregation, both for presenting useful data in the UI and also to keep our backend scalable. We don't keep around particular aspects o
15.
by wycats 9y ago
For clarity, we also support almost all Rack-based frameworks in Ruby (including Sinatra): https://www.skylight.io/support/advanced-setup We should probably update our copy to clarify this point in the prominent places
16.
by wycats 9y ago
For slightly more context, I wrote the first lines of Rust code for Skylight as a spike at the end of 2013, and joined the Rust core team more than a year later. :) I was largely inspired by a blog post in June 2013 by Patrick Walton: Remov
17.
by wycats 9y ago
> Preferring implicit code is optimization for the first person writing the code while making it harder to understand, debug, and update. I feel that this argument has been repeated so often that it's almost understood axiomatically
18.
by wycats 9y ago
Since this thread is somewhat rehashing the old arguments ("you write once, but read many times, therefore EIBTI"), it might be worth reading a more modern take on the topic by Aaron Turon of the Rust core team in his essay about
19.
by wycats 9y ago
Also, this particular format is the "wire format", which is the compact representation that we compile templates into to send to the client. The client then compiles that representation into flat opcodes, in part by specializing t
20.
by wycats 10y ago
I grew up as an Orthodox Jew and virtually all of the stories of the bible are heavily illustrated in many forms, both recently and in ancient times. The fact that the Megilla doesn't contain the name of God is an interesting phenome
21.
by wycats 10y ago
I don't agree that all orthodox jews subscribe to it, although I do agree that it's a commonly held belief. The universal values held by Orthodox Jews are the articles of faith of Maimonides ("Rambam")[1], which are incl
22.
by wycats 10y ago
Further, Maimonides, who enumerated the principles of faith accepted by Orthodox Jews, also held that Genesis could/should be interpreted allegorically[1]. > Some medieval philosophical rationalists, such as Maimonides (Mosheh ben M
23.
by wycats 10y ago
> "favorite" wart at the moment: '% x ' parses to the literal string "x" - "%" when not preceeded by an operand that makes it the infix operator "%" starts a quote-sequence where the foll
24.
by wycats 10y ago
> My takeaway from this is that first-class cancellation tokens are the right approach, but languages need some kind of syntactic sugar to eliminate, or at least reduce, the verbiage for the most common case of propagating it around. Tha
25.
by wycats 10y ago
> I also read that as Google will refuse to implement features if it doesn't get it's way in how they are designed. There's no reason for Google to do this, in general, since there are enough Googlers in enough standards g
26.
by wycats 10y ago
I think it's very likely that we could avoid turning this into a zero-sum debate with one total-winner and one total-loser. That said, I think there's no positive sum because some folks believe that (1) Promises should be the prim
27.
by wycats 10y ago
TC39 member here. cwmma gets a lot right here: Promises have always been contentious in JS (and TC39) and Domenic has indeed had the patience of a saint attempting to wrangle the various points of view into a coherent proposal. TC39 as a gr
28.
by wycats 10y ago
Shipping without understand is no virtue, and as far as I can tell, there's no hard conflict between the two. The entire official story of "lean" is "build, measure, learn", which is fundamentally about developing a
29.
by wycats 10y ago
We should also consider making startups a place where understanding is more common.
30.
by wycats 10y ago
For what it's worth, I spent half the holiday weekend arguing on Twitter that I think apple has lost its way, and talking about my switch to Windows for my home machine, so I found both the vehemence of the flagged comment and the flag

More ›