jongala
I don't fully agree with it — for one thing, I think you can develop taste in a field without actively participating, but you have to engage with it beyond passive consumption. Basically: I think it's possible to be a good movie critic without making movies yourself. Given the collapse of the friction/effort side of things, I think that is really worth unpacking.
I have to say I find the debates about the post's style and em dashes pretty disheartening. There have always been plenty of good jokes to be made about HN's culture, but wow. For a community that has been snarky about fools counting lines of code for 40 years to be out here counting em dashes is pretty damning.
It's from 2021: Moiré no More (https://newsletter.shifthappens.site/archive/moire-no-more/).
Here's 2009: https://web.archive.org/web/20090307125843/http://www.baseca...
if you go back to 2007 you can see the same structure in a plainer presentation; it's easy to see how they went from one to the other: https://web.archive.org/web/20070831191822/http://www.baseca...
Pretty interesting!
For mine, I make fields by superimposing a bunch of harmonic functions. By playing with different periods, phases, etc. you can get some cool patterns that look irregular and interesting, though I think they have a different feel from some of these noise-based examples.
I also make some fields by using sources and sinks: a collection of points that push out or in. You don't need that many to make an interesting field.
For collision detection I use the trick @danbruc mentioned in another comment: I draw to an offscreen canvas, and just check pixel color to see if a trace is already there. It's probably very costly in terms of memory as a data structure, but it's very convenient :) https://www.instagram.com/p/CMi4QcXn6_y/?img_index=1
For me the interest has come in coloring the lines — by deferring rendering until after the path has been plotted, you can color different traces according to how long they are, how much they curve or change, etc. which can reveal interesting bits about the flow structure. https://www.instagram.com/p/CMvqZjkHYpV/?img_index=1
Thanks for this great writeup @tehrash, the explanations and examples are great!
Computer, generate a list of applications where technology like this should absolutely not be used.
This seems terrifying — wouldn't this, for example, synthesize identifying details about motor vehicles not present in the sample, drawn from training data? About people? Etc etc
This sounds awesome for making a consumer mapping product feel higher quality. Hell, it could even serve an anonymizing function that is pro-privacy ("a roof" not "your roof"). But it feels incredibly reckless to direct this toward those listed industries.
People in surveillance and forensics etc. should be confronted with the limits of the quality of the data they are using, we should not try to synthesize extra confidence in their analysis by making the images seem higher quality than they are.
I use this all the time to handle things like text, images, pdf etc to open them in non-default apps. I find this a lot easier than dealing with the dock. Hope this helps!
Like, even on cut or stamped grills, how much could performance be improved by e.g. sandblasting the finished piece from one or both sides and taking down the edges a bit?
https://www.engadget.com/2015-12-04-casio-and-the-sleng-teng...
This is a very interesting story, and it's great to see Okuda acknowledged for her work and hear more details about that. Casio is a great example of a company that I just took completely for granted growing up and seemed completely opaque and impersonal to me. It's so cool to see the individuals that are behind all of those things. My brothers and I had an MT-40 when we were kids, I loved playing with it, and had no idea it had an impact like this.
I'm not trying to discount the take-away that the fees are very high regardless of the projection basis, but I think it's important to understand the difference. If these criticisms are not clearly reasoned or communicated, I think that fuels the perception in the financial community that these complaints are hysterical and unfounded and should be dismissed.
> "Over the last 10 years, the return on those “public asset classes” has surpassed expectations by more than $2 billion, according to the comptroller’s analysis. But nearly all of that extra gain — about 97 percent — has been eaten up by management fees, leaving just $40 million for the retirees, it found."
Note "surpassed expectations" in there. That makes it sound not like the total return was $2B but that the return was $2B above projections, and after fees this was functionally erased leaving return at projected level. Am I misunderstanding the language here?
It would be great to be able to set buy/rent/stream filters alongside selecting providers. If you know you don't want to buy, for example, the current interface relies on a lot of clicking.
Nice work!
I was just speaking towards new paths in getting the most out of ICE-centered power systems, that an alternative power store and MGU can uncover better turbocharging options vs. a purely mechanically coupled turbine/compressor. These technologies are being developed at the less price-sensitive high end of the market, just as Tesla is doing with an all-electric drivetrain. They started at 100K+ roadsters, developed to an 80K luxury sedan, and are developing down market from there. I think it's totally appropriate to encourage a shift in industry standards, as you say, with incentives in this segment of the market (let alone where the Prius sits). It's a bit of an absurdity with the Porsche, but take heart that there are only 918 being made…
As far as what kind of sports cars we should be encouraging, even mid-market cars are so fast now you really can't enjoy them on the road. That's why cars that emphasize a fun driving experience at still-sane speeds are the most interesting to me now, like the FR-S, the Miata, the Elise, etc. But that's a separate conversation.
Some of the more sophisticated work here is also being done by Porsche in their LeMans program, which has (as I understand it) a uniquely complex turbo/hybrid setup.
I think it's really exciting. Considering this type of usage — mostly transient stuff — it's tempting to think of a system for sports cars with a supercap energy store that's lighter weight than a battery store. Toyota use supercap stores in their LeMans car, I'll be interested to see if that trickles down anywhere.
This, together with the huge budgets involved at the front of the grid, also produces a sport that features celebrity engineers who command multi-million-dollar salaries and have dramatic contract disputes, etc. This may or may not appeal to you.
Crucially (for me), the teams are very secretive about what they are doing and why, so figuring out the mechanical and aerodynamic approaches that are in play, which ones are winning, which brilliant ideas are languishing on underfunded teams, etc. becomes a very interesting saga of nerdy armchair detective work. Even the parts of the cars that they can’t hide — the bodywork — are sophisticated enough aerodynamically that you can’t necessarily tell what is going on (or copy it for your car) without a relatively detailed understanding of how it works within an overall aerodynamic philosophy. There is a good and growing online community to get into with that.
Then you add the drivers; there are only a couple dozen to know about so its pretty accessible that way, and you get a sense as others here have said about who is under pressure, who has the talent but not the machinery and vice versa, and how they all interact.
Another interesting interaction is between drivers and cars, or driving styles and car characteristics — there are drivers that can uniquely exploit certain car characteristics, or cars that may be designed to suit certain drivers or styles, etc. and those will evolve as drivers move among teams and as the technical regulations change.
I realize typing this out that these things point more to enjoying the sport more than the races themselves. I am a lot less fixated on watching the races than I used to be, but there are still some great moments and I catch what I can. Today’s Russian GP was notably boring for the last couple of years, FWIW. For more instant gratification Moto GP might be a better bet, and most of the technical drama unfolds over there too. I still think F1 is pretty exciting though.
To the extent that the executive-level perception of design's contribution to the success of an enterprise is important, then yes, for sure: we should all make sure that the investments we make in design are substantive and focused on supporting the overall utility of what we are doing, and don't create a perception of wasted resources.
But he (to my mind) basically runs down and says that Carousel is mostly redundant in the existing photo management marketplace and hasn't had good traction; Paper is mostly redundant to Facebook's own existing app and can't find traction; and Jelly is fundamentally off target in its premise and doesn't have traction. The fact that all three had significant investments in design, and tried to showcase that investment to users, does nothing to implicate design in their failures or invalidate design's status as an essential focus for businesses.
It's a thoughtful and interesting article, but after a first reading I just don't think it holds up beyond the author's anxiety on behalf of the discipline, and/or sense of missed opportunities for talented designers to have some high profile hits.
And good find on Register -- I think part of my confusion or displeasure with that face is that I was already familiar with Stratum, and in all-caps they are pretty similar (lowercase characters are pretty distinct between the two), so I thought someone had added traps to Stratum just to be different or cool. I now see that Register predates Stratum by a few years, which is interesting also.
I still prefer Stratum …
EDIT: OK, check these out: http://i.imgur.com/0ovnO49.png
The "best" system would be to use a fuel flow restriction — X g/s of fuel, with the usual restrictions on fuel composition. The designer's job is then to extract the max usable power from the chemical energy in the fuel. This would make for really exciting development and diversity, and make F1 development a true laboratory for other transportation and power production contexts.
It would also be prohibitively expensive and probably result in one manufacturer in a walkover for a while, until others could switch architectures. Experimenting with different architectures is a huge money pit, and is why the prescriptions for 10 and 8 cylinders were in the last couple sets of regulations. Just working out the competitiveness of V12 vs V10 vs V8 was getting unreasonable, let alone dealing with different hybrid setups on top of that.
It is also my understanding that the accuracy of fuel flow meters has not been considered good enough to provide adequate parity in a racing environment, when fractions of a percent can mean the difference between winning and losing.
The new F1 rules do include fuel flow metering, although it is based on kg/h and I don't know what kind of spiking is permissible. The regulations are as detailed as they are, with specifications for power transfer among components, etc. to spare teams the expense of experimenting there and to give them targets to optimize for. See jdietrich's comment: https://news.ycombinator.com/item?id=6952583
It is pretty discouraging with respect to the purity of the formula, but it's kind of a fact of life. And I think the development of turbocompounding and pre-spooling turbos with electrically stored energy to avoid lag is really exciting, and the future of combustion power on the road.
Helvetica is indeed cool (the Neue family cooler, IMO) and has been since the 50s, and _Helvetica_ is also cool. Thinking of Helvetica as the only worthwhile sans-serif typeface is less cool :)
The sed/xargs/etc. examples look increasingly like impossible-to-memorize line noise to me, while the --include, --exclude etc. options in `replace` are comprehensible and seem to follow standard command line argument practices.
Again, this is from a very entry-level unix tools perspective, but there it is.
It also seems to me that reimplementing things with the stated goal to make them easier to use has to be one of the best justifications around, no?
I hope I sound as respectful here as you did in your comment -- I certainly appreciated seeing a clear response to her library, so thanks for that.