To be honest, I trust you, even as a random stranger on hacker news. But I don't trust that you'll never sell this, and I don't trust whoever you you might sell it to.
1,306 karma · joined August 20, 2013
To be honest, I trust you, even as a random stranger on hacker news. But I don't trust that you'll never sell this, and I don't trust whoever you you might sell it to.
Unlike OpenSCAD, it's built off of an interactive BREP modeler with a real kernel so it's as easy to use as a regular CAD system for those who don't want to code. Actually the interactive portions of Onshape are a nice example of how to get WYSIWYG elements into a non-WYSIWYG application.
I imagine theres some protocol to tell the controller the cube is solved (e.g. only turn it on in a solved state) and it just tracks moves from there to determine the current state.
In practice, I imagine if California passed a state amendment fixing themselves to PST, the federal government would either change the law or refuse to enforce it. Opposing such an amendment would be pretty unpopular.
But in theory, the federal government does have power to "fix the Standard of Weights and Measures" nationwide. I see no reason for a court to rule this as being outside federal jurisdiction.
Some interesting musings in this realm: https://marckhoury.github.io/counterintuitive-properties-of-...
It's purely a novelty, of course. But a cool one.
Just a voice saying "Hi, I'm a bot, can you describe your issue?", followed by "Okay, sounds like a whizmo issue, can I transfer you to our whizmo department?" seems potentially both faster and more accurate than a huge options tree. That's a win even if the AI can't directly resolve your issue.
I'm curious, how does it compare to google's own similar product, Backup and Sync[0]?
It seems like the primary difference (other than being FUSE-based) is that, for data where google has a collaborative interface (docs, sheet, etc), Backup and Sync will place into the folder a "file" which is simply a link to open up the docs/sheets/slides app. Your app, on the other hand, seems to translate this data into open office format when changes are detected (i.e. .ofd for docs).
At first glance this strategy seems less good for real-time collaboration and less performant, but there may be advantages to it as well.
Do you find that strategy to be practical in most cases? Are there other features that distinguish this from Backup and Sync?
EDIT: Aha, looking into it more, it seems like mounting drive folder with this project doesn't trigger the downloading of any data, and rather lazily loads the data when the file system requests it, which would be a very significant difference. Is that right?
But I'm still confused on one point: It seems like the supreme court has already ruled that the 8th Amendment applies to the states in Roper v. Simmons[0], Robinson v. California [1], and others. To me this pretty directly means that a state law dictating a cruel and unusual punishment is unconstitutional.
So if supreme court isn't deciding whether cruel and unusual punishments at the state level are unconstitutional in general (a previous ruling), and it isn't deciding whether this specific civil forfeiture was cruel and unusual (a decision to be made by the state court), what exactly are they deciding? Is there some unplugged hole in the middle, like whether any CF case (regardless of details) could be cruel and unusual? Or is there some other reason that the previous rulings don't apply here?
Lockhart's lament is thrown around here a lot around here, and it does make a valid criticism of math education. On the other hand, I think we're justified treating math differently than art. We tell students that math will be useful because it's true. Math teaches you that viewing problems more abstractly will make it possible to gain more insights into them, and math provides frameworks for making those insights. This skill takes practice. More than most skills, it's clear when you're doing it well, which makes practicing it all the more effective.
Math is beautiful, sometimes. I see this article saying the mundane parts are worth fighting through, too.
From what I can tell, these two economic theories rely on competing assumptions. Keynesian economics is the theory that results from assuming the size[0] of an economy will closely follow the amount of aggregate demand. Neoclassical economics is the theory that results from assuming the size of an economy will closely follow the amount of aggregate supply.
In microeconomics there is no such duality. Rather, there is an understanding that supply and demand are each elastic with respect to one another. We measure this and reason amount markets while thinking about two explicit quantities: the elasticity of demand and the elasticity of supply. The two numbers (and the ratio between them) will tell you a lot about the effects that various conditions will have on a market.
My question is: Is there a corresponding concept of e.g. "the elasticity of aggregate demand" in macroeconomic theory?
If so, could articles like this be made more objective by providing concrete measurements of this figure on some time scale, rather than subjectively stating things like "Keynesian economics is hot again"?
If not, what prevents or complicates the existence of such a quantity?
[0] Please correct me if I am misusing this or any other economic terms and concepts
By contrast, replacing a full meal with whey protein takes a stance on what you should and shouldn't be eating vs general dieticians' recommendations (and the FDA's). I wouldn't recommend replacing most meals with either one, but if I had to pick the fad diet, it'd be whey.
Also, warrantees force companies to bear the full cost of their negative externalities. In lots of markets, companies will come out ahead by not fixing or replacing your product (brand damage < actual damage), so those businesses are motivated directly into misleading consumers into buying worse products. Sounds obvious, but clearly that's not good for a society in the long run.
There's not a way to subscribe to it, though it's not obvious how a subscription would work. The summary of any given day is not finished at the end of the day. Rather, the set of articles for that day, their summaries, and the articles themselves will all continue to grow as more information is gathered. So, it is a good way to "catch up" after some time away from current events. But to my knowledge there's no coordinated effort to "finish" a day or a month by any deadline.
I'm talking about is a platform where my decision to click/watch content is based on reviews and recommendations, not loud design and attention-grabbing headlines.
In that world, the subscription model could make sense and content aggregation could make sense, but neither is required, nor does either addressing the issue on its own.
- Non-fiction books
- University-centered online courses
- Documentaries
- Some of Netflix's original programs
- Wikipedia's monthly news summaries
- The "Great Courses" on Audible
These media aren't thoroughly monetized on a pay-per-attention-stolen model. They're more optimized around having good reviews from friends and online.
It makes me wonder if there might be the possibility of a Netflix for news, where a 3rd party curates and allows ratings of lengthier pieces on long-term issues, interviews with important figures, and 20-minute investigative reports (like I remember seeing on 60 minutes). Naturally, this wouldn't work for up-to-the minute news where everyone's attention is driven based on who's got the latest break, but it seems like it would work for these other things. It would still give the "lunch conversation" motivation, where people could talk about whatever was released in the last few days. Certainly it sounds like a less attention-assaulting place than the current state of news.
In Java (and JS) there's a separate, all-knowing garbage collector, while swift is reference counted. In an ARC runtime, the didSet/willSet distinction avoids explicit calls to release the object, which is pretty clearly a good thing on the programmer's end. You can debate whether the benefits of full garbage collectors outweigh their performance characteristics, but given ARC, the didSet/willSet distinction definitely makes sense.
Hofstadter said in GEB (in 1979) that the only program that could be capable of beating the best humans at chess would need to be a general and human intelligence... human enough to decline your suggestion to play chess, and suggest you talk about poetry instead.
It seems that people today are still engaging in the same sort of fallacy. I keep hearing that deep learning is too hyper-specialized, that it's a tool and not an intelligence, that we're still waiting for a revolution of general intelligence, where intelligences will have sophisticated logic and make their decisions without billions of data points, just like humans do.
My counter-hypothesis is this: Computers, compared to humans, will always be more data-hungry (i.e. worse at making general decisions without huge amounts of data) and more data-capable (i.e. better at making decisions with it). And this isn't really a bad thing. We will still see revolutions allowing more and more general problems to be solved, revolutions allowing more and more general data to be considered, and revolutions giving more and more usable interfaces for inputing data and specifying problems. We'll still see data-driven intelligent assistants and data-driven board members making critical decisions like in everyone's utopian dreams/dystopian nightmares.
But these foretold "general" intelligences, who don't need excessive data, the intelligences who beat the Turing test, the intelligences who "want" things and "feel" things, who attempt to solve the problem of replicating humans... those come unimaginably far in the future. And when they do arrive, they won't really solve any problems that the data-crunchers haven't already solved better.
It is possible that a setup with high-precision absolute measurements can produce high-accuracy relative measurements, but the former does not imply the latter (imagine, for instance, any source of error in absolute measurements that's locally non-linear).
You're right that the short-term effect of this is indeed inflation on the prices of these needs, but the long-term effect is larger portion of the economy dedicated to filling basic needs instead of superfluous luxuries.
He had instinct for how the layout engine will do best, how to make really clean and reusable structures, how to get smooth animations running. This instinct was totally infectious. It had an impact on our culture around CSS (taking it seriously and doing it right the first time) in the same way that having someone who really knows logging, or concurrency, or db transactions, can really make an impact if they're there near the start.
Along the way lots of people assumed he knew JS, which if anything probably enforces the article's point. But before us he was just a smart guy whose side projects involved reskinning CMS sites and making cool CSS animations.
After a year of avoiding it he did start writing JS, and being honest, our app is pretty unique for needing that much love at that level — A year of time just doing structural, design, and layout changes is totally not warranted, almost anywhere.
However, I think there _is_, often, a false hierarchy that tends to build up among developers, where somehow, all server work >>> all JS programming >>> all design thought. This cultural "legitimacy" ranking, at best, leads to people letting horribly incoherent styling pass code review without a second thought. At worst it means high turnover in the people at the "bottom" of that totem pole who feel disrespected. As someone who spends 80% of his time on the server side I think this is an important bias to be aware of.