skysight-inc/HackerNews huggingface dataset:
> write your app against S3 and call it a day.

... and then later you notice that you need a special SLA and Amazon Redshift to guarantee that a read from S3 will return the same value as the last write.

Even S3 is only eventually consistent and especially if a US user uploads images into your US bucket and then you serve the URLs to EU users, you might have loading problems. The correct solution, according to our support contact, is that we wait a second after uploading to S3 to make sure at least the metadata has replicated to the EU before we post the image url. That, or pay for Redshift to tell us how long to wait more precisely.

Because contrary to what everyone expects, S3 requests to US buckets might be served by delayed replicas in other countries if the request comes from outside the US.
Conclusion: Officials in counties more likely to experience a Covd19 increase due to the political attitudes of their constituents, were under higher pressure to not mandate masks.

Oh I'm sorry, did i just ruin your beautiful correlation that you thought was causal?
I am tired of that too, but you can use the checkbox hack to implement features such as tabbed content for which storing user selections in the browser's history would probably result in unintuitive UX.
> The only way it can truly not affect anyone else is if no one else knows that you use ligatures

That covers 99.999999999% of the times ligatures are used then, that's my point.

Sure, in a situation like screensharing, using ligatures "affects someone else". A font also "affects someone else". A theme also "affects someone else". Night/dark mode also "affects someone else". That's a given. It's also something that is normally trivial to turn on or off.

And sure, very, very occasionally people use custom fonts with ligatures turned on in the CSS on websites.

> I think it’s fairly clear that for most people in most circumstances, a light background is superior to dark, and ligatures are a bad idea.

It's not clear at all. Regarding typefaces and character sets and reading comprehension, what a person is used to reading turns out to be the easiest thing for them to read (why do you use a monospaced font in your text editor?). I get that it's a fun thing to argue about because it is completely stylistic, context-sensitive and personal and has near-zero real world effects (I'm doing it now!)

> But ligatures change the actual glyphs, so that your fingers must type something other than what your eyes see, and any viewer must decode the ligature’s meaning.

As opposed to typing a collection of "actual glyphs" which the viewer must then decode back to their actual meaning via the conventions of the language? The characters available a given programming language are determined by [sensible] technical limitations, so creative use needs to be made of those to represent concepts that are already represented by single, well known characters that are not available in the PLs character set.

My beef is that talking about which fonts you like/dislike: that's a productive discussion as they're a personal thing, very often an aesthetic choice.

But banket saying "usage of this _type_ of font is bad": that's not productive in any way, it's pointless, as it ignores the huge % of people who clearly don't share this view. Saying "it's fairly clear ligatures are a bad idea": no, it's display preference, and if is forced on you, you will generally have agency to request it be changed back to something you are used to.

And this is every time coding fonts appear in HN: comment after comment stating the latter as if it's some empirical truth when it most definitely is not (and yes, similar thing for tabs Vs spaces etc, so obviously everyone paints the bikeshed, but this time it's completely tied to one person's personal computer display)
I am actually using PaintShop Pro 7.04 until today. It is good enough for 95% of my bitmap graphics work and it just feels so easy to use.
I noted below, that product people like Marty Kagan, consider a MVP to be a prototype where you test hypotheses. Worst case it can be discarded and a "real" product will be built after testing. It is a bit unfortunate in this that the "P" in MVP stands for Product.
> But that also means you need to have IPs that will last for as long as your client lasts.

It sounds like implementing this scheme without a method to rotate IP addresses would be a mistake. But maybe I'm missing something.
> This attitude that worships tradition is stifling innovation. I would much rather we stopped taking it seriously.

OMFG with the butt-hurt laziness. Jesus. You're taking it as the professional musician conspiracy being your mighty oppressor, but what I meant is, being a musician takes work. There is no way around it, we are wired to hear it. The keyboard as it is is laid out for efficiency. If you have for instance a keyboard with only 12 keys on it, plus 2 for up/down keys or something, well now you are at 14 keys in addition to thinking about when to modulate, so we are back to square one in terms of complexity. Music is complex, get over it.
The crazy idea that Ruby "DSLs" are neat is one of the worst things to come out of Ruby. This code is Ruby, and yet you're encouraged to think of it as a different language that's "intuitive" and "expressive" when you can't even tell what is executing and when. It's a nightmare for anything except the samples.
I am sure Google would love to see an end to the negative press, i also started a reddit post https://www.reddit.com/r/GMail/comments/jyrkq7/id_verificati... you can't stop discussing it until they create a big ticket for it https://issuetracker.google.com/issues
Did you know that the term for a female Gimp is "Glimpse"? :)
I still remember that time I tried selecting something and moving the pixels of my selection, rather than the whole layer in GIMP. I ended up having to google it and it was a 3-key combination shortcut. I don't remember how to do it in photoshop, but I'm pretty sure I didn't have to google "how to move a selection" that time I used it.
True, but if everyone did that, there wouldn’t be any Apple engineers left to fix the damn software itself, because they’d all be running 24/7 support for millions of angry users, answering the same damn questions and complaints again and again and again.

If that is their intended process, then it is such a false economy that it warrants firings all the way up to the board.

This is why we write documentation—good documentation, that explains the product and how to use it, and anticipates the common problems that users run into and guides them through those as well. So that users can handle the day-to-day stuff and only need to interrupt its developers for the exceptional cases that no-one has anticipated—which is as much about the developers learning what more they need to fix as about getting users over that hump in the meantime.

.

Apple is absolutely, notoriously, abominable at documentation, in part I think because Apple really absolutely hates to admit that its shit ever smells too. But if you can’t own your own mistakes, then you’re never going to fix them and get rid of that stink.

Honestly, I really miss their old NeXt-derived docs from back in the early days of OS X, both in their content and their presentation and navigability. I mean, they weren’t brilliant—good on the Whats but not asogreat on the Hows—but compared to the slop they’ve been serving users these last 10 years those docs were an absolute masterclass. Or even look at Microsoft, who * and* accept their APIs are complex and difficult, and so document the tar out of them so their users can mostly get by for themselves.

.

The other problem is, the health of the developer platform today isn’t immediately, directly reflected in the size of the next quarter’s results. So when the company’s run by and for the beancounters and shareholders, without regard for what the engineers are telling them, they don’t see the need for greater long-term investment. I mean: everything works great now, just look at the size of those revenues!

It not till years later that the knockon effects of those poor upstream processes and resources reach the surface, at which point the damage is far more severe than it ever should have been had they nipped it at the start. Just ask the formerly engineer-led Boeing how that whole McDonnell-Douglas pennycounting culture is working out for them now. Yup.
Ah, but you missed my point :)

Maybe you aren't seeing Lisp itself in production code (although someone suggested Emacs which is Lisp), but you see it's ideas and influence in almost every language and program you'd find today. There's little bits of Lisp everywhere you look, even if you don't recognise it as Lisp.
Great for perspective. Thanks for sharing!
> mostly a very tiny crud layer & a little bit of business operations.

Even if you have a SPA, which isn't a given (yes, trends. I know. They come and go), the API, data migrations and background workers can easily be 50% of your code and effort.
WhiteHat Jr’s founder files $2.6M defamation suit against critic
Exactly my experience. Been working in fintech for 15+ years. Went through 4 tier 1 banks and a few smaller ones. Most popular languages are cpp, java and sometimes even c# or ocaml.
Never did I hear cobol even being mentioned.

Just wondering how true those statements about cobol still being so popular are...
plenty of non-paywalled sites to link to...why link to a paywall?

Also, jan morris was an excellent travel writer
I'm currently using my old iPhones for doing camera-trap photography and videography. I've got a 5s recording some bird feeders in my yard, for example. Decent camera for filming during the day. Unlike my DSLR, it's not artificially constrained to only recording 15 minutes at time. It's tiny, and if I have it near an outlet I can even power it so I don't need to worry about recharging it. It also does slow-mo if you don't mind going down to 720p. I think an iPhone 6 can do slow-mo at 1080p.
Both, Photoshop and GIMP are really complex programs with steep learning curves. I tried to do some editing in Photoshop, since I now have a license, and I was totally lost. I tried to add some guides so I could draw a rectangle to cut a image. I tried dragging from the border of the image, as I do with GIMP, and no way. So I resorted back to GIMP, not wanting to spend half an hour trying to learn how to select and cut an image in Photoshop when I already know how to do it in GIMP.
Automate your Jira Excel reporting with Python
Jessica's advice is a bit different compared to other advice from other successful founders. I remember someone said, a startup needs a builder and a seller. But here, Jessica add one more person which is someone who has determination. Interesting!
The small 24 drive all flash model (dual controller) is around $20k, based on a quick google search
This entire thread is flawed in two fundamental ways:

1) The primary concern here is per capita road damage. If that's agreed, why is the conversation not about improving the resiliency of roads?

2) Why would the adoption of new technology automatically subject you to draconian taxes that have nothing to do with that new technology? I understand infrastructure needs to be paid for, but this is simply a cash-grab by politicians. If people started jogging to destinations rather than use cars, would it be acceptable for the government to charge a "jogging transportation tax"?
It's interesting that you use the word "curation" to describe designing for literature. Lately I have been looking into how museums put together exhibits and how to integrate some of their approaches into web or print publishing.

It feels like so much of what you described is lost today ie., skill and decorum in displaying words meaningfully. If I may ask, what are some personal design principles that you look for when critiquing a publication (be it print or on the Web)?

For the record I am not employed by any company or agency, I am only an individual who is trying to get a better understanding of what I should be looking for as a consumer and creator myself. To boot, I appreciate your insight and the thought processes behind it. Thank you!
In this day and age I always verify the authenticity of downloaded ISO images, but this seems not possible with Tinycore Linux as no signatures are available, which makes me somewhat uncomfortable.
If the small keyboard was better for everyone then presumably we would already have them. But my guess is that a keyboard that's too small is just as bad as a keyboard that's too large, so the current size is a compromise based on the average hand size of pianists in the 19th century.
I didn't learn to ride a bike until I was 39. Motivation was that I had just taught my oldest daughter to ride and I wanted to be able to go out with her. Also proving that yes, it is possible to teach people things you have never done yourself.

I picked up a cheap hybrid bike (about $250) from Dicks Sporting Goods and just started putzing around the backyard until I felt confident enough to go out on asphalt. Took a week or two, then I was out cruising the neighborhood.

I don't consider myself good at all, but now I know how to do it.
What's the license for project? It's a bit odd to see a serious opensource project without any license specified as it prevents adoption for at least some of potensial users. I for example pay close attention to licensing as a personal user. It's just too risky to invest my time learning to use project which can any time in the future become paid or restricted in other way.
You'll be wanting Glimpse
https://glimpse-editor.github.io/
Someone needs to implement Go in the JVM so it can finally have a good GC
Straight up BSD from the CSRG at Berkeley had an absolutely abysmal virtual memory subsystem. Processes had very small and hardcoded VM size caps in the kernel, and some algorithms that worked okay with 1 or 2MB of RAM were scaling poorly with the massive 4 or 8MB systems showing up.

Despite being meant as a research system, Mach2 was effectively 4.3BSD with a good, fast, and scalable VM system. I imagine this had to play a role.

(The Mach VM would be reabsorbed into 4.4BSD and inherited by all the *BSDs -- it's since been replaced in all AFAIK, but still interesting)
Ah. I see. I wonder if they're not just hiding a lot of complexity like that; I mean once a component becomes decently complex, that there's no way for you to implement it right without learning Vue.
Which is mostly popularized by new kind of programmers breed who learned everything purely from YouTube.

They don’t know their tooling, systems, how web apps works, make huge mistakes on each level. Just putting the one solutions they know in everything.

Or—bear with me here—it’s possible that everyone other than you actually isn’t an idiot and there are issues that you are neatly stepping over with this patronising nonsense.
I think there could be a middle ground: rent control that allows increases that average what the free market would follow (this can be determined by looking at how rent is changing in non-rent-controlled apartments), or even a few percent higher than that. This will stop landlords from doing vicious increases, but also will prevent renters from acquiring absurdly low rents.
Don't ever work on a COBOL modernization project. It is a career killer with little to no upside. COBOL systems and the people directly using them are Chernobyl.

Both government regulators and operations personnel have made careers out of trusting black boxes that no one fully understands anymore.
Regulatory specifications are ambiguous and disorganized. Imagine working with someone who knows that you are trying to shed light on the technology that they were responsible for, yet do not fully understand. How cooperative do you think these people will be with your efforts? How do you think the managers responsible for this work survive the politics of the project's inevitable failure? Blame rolls downhill. Modernization projects require strong leadership and collaboration across many teams. That's a huge problem because such an environment very likely does not exist in the world today. No one understands how the algorithms work or even how they should work! Forget how challenging it is to work with COBOL, which someone could eventually figure out. Whatever you've written has to be tested, and you don't have a trusted source of business logic from which to verify how it ought to work. You only have the black box.

If you've been given this task, start interviewing at other companies. You were given a suicide mission by people who are well aware of that.

My experience with this was with regulatory margin trading systems supporting a multi-billion dollar market.
Or more probably the company using them folded...
I don't know Matestack specifically but in general the problem of DSLs is that they can quickly turn into giant pain in the ass once you need to do something they aren't prepared for. And this has bitten me enough times already(ActiveAdmin, Thor,...).

The other problem is that if you use this you only learn the specific DSL which isn't portable. But if you use and learn the basic technologies under it - HTML, CSS, and pure JS now that is something you can use elsewhere even if you throw Ruby away completely. And the knowledge of the basics is really really important and useful.

Anyways, what is a problem with writing good old .html.erb templates? I don't think there is any.

And for the reactivity thing - the most easiest and fastest(10 minutes at max to install and enable) is to just turn on Turbolinks[1] and include this little plugin[2][3] for persistent scroll position where you want. Now when when you click marked with `data-turbolinks-scroll = "false"` Turbolinks fetches the page, replaces the current page with it, and you are still at the same scroll position. No need for SPA or JS heavy FE or anything.

[1] https://github.com/turbolinks/turbolinks
[2] https://medium.com/@kosovacsedad/how-to-turbolinks-5-scroll-...
[3] https://gist.github.com/sedadkosovac/661d0fd369069cad010f164...
Macsyma and REDUCE are written in Lisp. The development of those two computer algebra programs started in the mid/end 1960s. They are still maintained today. That makes them over 50 years old.

Some history on Macsyma:

https://www.sciencedirect.com/science/article/pii/S074771711...

REDUCE:

http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.153...
For those who haven't seen this old joke, Bruce Clement suggested in SIGPLAN 1992 that OOP COBOL should be called "ADD 1 TO COBOL GIVING COBOL".
> streamed over a websocket

That's my problem with this approach, I wonder what the penalty is (performance and complexity wise) for going that route. What is it using for websockets btw, Action Cable?
Incredible work.

What's most impressive is they've separated the rendering algorithm (Mitsuba 2) from the retargeting framework (Enoki).

Enoki look amazingfrom their paper. It supports vectorized CPUs, JITTed GPUs, forward/back autodiff, nested array types.

Mitsuba 2 then expands that range even further by templating on key types and operations. For example, a materials color property might be represented by a RGB tuple for basic rendering, or an array that captures the full spectrum of light frequencies for a spectral renderer. They supply some example code, which is absurdly clean, as it's devoid of any specifics of storage and calculation, and focusses just on the high level algorithm.

They claim that the GPU impl is superior to PyTorch / TensorFlow in some regards as it can split the difference between eagerly sending every operation to the GPU, or processing the entire graph at once.

The amount of work and understanding to produce something like this is insane - they just casually mention how they've implemented a novel light transport scheme, an "extensive mathematical support library", and sophisticated python bindings.
You're just redefining "religion" so that the claim is a tautology. You could do this with anything:

"Everyone has a God (where 'God' means 'favourite thing')"

"Everyone believes in the existence of Hell (where 'hell' means 'being unhappy')"

"Everyone believes in the possibility of "salvation" (where 'salvation' means 'self-improvement')"

Redefining words so that the original sentence is correct is a tad too "charitable", particularly when the new definition is completely at odds with how everyone uses the word.
Google Cloud CEO Says Open-Source Clouds Are Critical for End-User Control
The license is clearly there. It’s GPLv3
Yes and no. The design includes a custom built 16-bit CPU, which uses a custom instruction set, which I wrote an assembler for. There is a small 4kb bank of RAM that contains a program written in this instruction set. From a hardware perspective it is just data, but from a a software perspective it's that program that is ultimately responsible for running the game (by reading input from the gamepad module, setting up GPU registers, etc.).
There are other layouts, like Janko. Manufacturing pianos is expensive, so these are mostly created as 3d printed overlays by hobbyists.

https://en.wikipedia.org/wiki/Jank%C3%B3_keyboard

https://www.facebook.com/groups/janko.piano

Bill Wesley also has the Array system which is somewhat related, but haven't seen that for piano.

https://www.arraymbira.com/the-array-system/
Eventually someone will find a coincidental or unintended aspect of your API and then depend on it. This article is the ultimate exemplar of this rule.
It's also what gives you this funky syntax:

class Foo
class << self
def bar; end
end
end
I'd find it very weird if there was some platform team member responsible for app installations who's not familiar with GIMP.
Sure but you'll almost certainly only ever going to be able to play in your own home. Though - if Alicia de Larrocher (one of the 'greats') 'at less than five feet tall and with small hands for a pianist spanning an interval of barely a tenth on the keyboard' could manage both Rachmaninov concertos I'm sure you can. She was highly inventive with her fingering!
What's the best RPi alternative in your opinion?
I traced my Covid-19 bubble and it's enormous
Yea, I have switched to Django with the intent of continuing to develop primarily SPAs.

Like I said in other comments I'd only build an API in Express if I needed its particular performance characteristics.

I've checked other tools in the JS ecosystem that serve as "low-code" API layers, but upon close inspection they always seem to have some limitations on the business logic you can write, and some of them lock you in to products. No thanks.

I'm finding Django REST gives me a sweet middle ground between dev speed backed by great abstraction "magic" and freedom to customize as the app grows.
Public education is not “free”, we pay for it with out taxes. And right now we are paying, and our children are not getting an education...
alps was created by the same person who started maddy, by the way.

It is not me. Just wanted to give a little tribute to the amazing person who put a lot of work into email libraries for Go: https://github.com/emersion/
Humans are unique in that our rational reasoning is strong enough to reliably override or control our intuition and feelings. Remove that and we are just a normal mammal. Add that to other mammals and we could integrate them in society as full citizens.

For example, we aren't using millions of mammals to sit and label machine learning models all day. It is not because they can't create those labels, mammals are really good at a lot of tasks, it is because we can't make mammals sit and repeatedly do a task all day even when rewarded. They just lack the reasoning capacity to override their intuition to do it.
Build a replacement…what? iPhone? Exploit for letting you have private entitlements?
Currently the license is GPLv3, you can find it in the COPYING file.

There are some messy bits related to licensing because it was MIT licensed in the past (back then when I did not take this "little pet project" very seriously).