Hacker News new | past | comments | ask | show | jobs | submit | more cestith's comments login

Nobody Wants This; Bridgerton; Wednesday; Man on the Inside; 3 Body Problem; Emily in Paris; the live-action Avatar: The Last Airbender; Love, Death, and Robots; How to Sell Drugs Online (Fast); Is It Cake?; Everybody’s Live with John Mulaney; and some others I’ve definitely had conversations about outside my own household.

Arcane was a pretty big deal and it was released on Netflix and TenCent.

They also have continued series that originated on other networks, including Unsolved Mysteries and Black Mirror.

I know several people who watched Cyberpunk: Edgerunners on Netflix and are excited about the upcoming CDPR and Netflix project set in the Cyberpunk universe.

I’ve had recommended to me and have recommended to others quite a few of their original movies. You might like 6 Undergound if you’re looking for an action movie.


Also, Netflix kicked off the streaming premium shows with House of Cards and Orange is the New Black.


Love How to sell drug online (fast), surprised to see it listed here tho 'cause I've never heard anyone talk about it. Considering it got 4 seasons, it must be popular tho.

And yeah, Bridgerton, Wednesday, Emily in Paris, and 3 Body Problem each certainly take their moment at least in my circles.


I mostly like to choose a data structure that's handy for modeling the data I'm worried about first. Then I write code to manipulate that data, including getting it into and out of other formats if necessary. Then I worry about what the application really needs to do with it. Once everything's a presentation or transformation of the central data structures, the code becomes fairly obvious. One I have the data handling and the UI, often the UI is just another case of presenting or updating the data.


For some applications, like an API-driven backend made to serve other applications, you can consider that the API itself really is your UI. It's how your users interface to your code. Your users just happen to be other developers whose code had it's own UI too, maybe a text or graphical one or maybe another API.


Good point. I was interpreting "UI" as "GUI".


Exactly. A web api, a CLI... It doesn't have to be graphical.


It is MIT licensed so one could host their copy or fork entirely elsewhere. It's available as a Rust crate, which doesn't seem to have the issues that concern you. The Discord part is a little harder to address. Contributing back to the code upstream could be difficult. Projects have moved before when corporate hosts proved problematic for either the maintainers or enough users, such as the exodus from Sourceforge. I have no doubt if Discord, Github, or Twitter become issues the project could move elsewhere, possibly to a private Gitea and to Mastodon. Right now, though, the maintainers are probably happy to use these services and not worry about maintaining production servers for it.


Use them, sure. Suppport them, sure. But require them, nah. Vendor lock on them, nah too.


So you're suggesting that the maintainers should fragment their community by officially supporting Mastodon and Discord and GitHub and GitLab?


The community and their own time dealing with said community would both be fragmented. I have a feeling what they most want to do in maintaining the project is to spend time maintaining the project, not the infrastructure for distributing and supporting it.


They can at a bare minimum point to say an IRC #room on Libera.Chat and say it's unofficial, so folks can know where to congregate. In the case of Mastodon or other Fediverse, make that the official and have that forward to Twitter if you cared. GitLab (which isn't the only alternative Git forge) itself lets you add to merge requests via patches and emails--along with supporting automatic mirroring. You can make one just a read-only archive. You can also just support two platforms--or drop the problematic proprietary one.


Sometimes the modular system is very flexible and straightforward. Other times the system really is modular, but makes many assumptions which make little sense to and are even difficult to foresee by someone less familiar with the overall system. See all the years of discussion over libraries vs frameworks vs complete code ecosystems. If I have a three week deadline and it takes three months to come up to speed with your system's docs and code, I'm going to ask for something without an up-front PR before I take it on myself.


I used to see a lot of them in conferences where college students or industry folks had them for note taking and had a bigger, bulkier, more powerful computer elsewhere. As a primary computer they were lacking, but as a second one they were cheap and easily mobile.


The tiny keyboard combined with my oversized hands made it really hard for me to justify as a note taking tool haha. But yeah, I definitely can see them being used for this purpose. Especially since the laptops of that era weren't particularly lightweight either.


The US is a pretty big counter example. It's two major cities on the Atlantic and Pacific coasts. That's a round-trip flight at least for people in most of the country.


That's not a counter example? That's still 'in-country' and not Estonia.


Oh, sorry. I read your post originally as in-country meaning not cumbersome, as opposed to potentially cumbersome but less so than having to go to Estonia in person. Yes, New York and San Francisco are domestic for US folks obviously.


APL is extremely high level but terse. Brainfuck is extremely low level with a very limited alphabet of input tokens. The two bear really no similarities.

People who decry Perl as a "write-only language" have very rarely given Perl more than a cursory look. It has a lot of syntax, yes. It uses some shorthand symbols, yes, but not to the extent that APL does. The complaints about Perl from C or Python fans are just the same complaints Lisp folks have about C or Python syntax. Most of them are quick to proclaim how superior Python is. Oh, but Perl doesn't have invisible syntax nor a global interpreter lock.


Perl had the same problem as C++ and before that Ada have. There’s just too many ways to do things, so everyone use their own subset of the language and their own idioms. Which means that it’s hard for someone else to understand what you have done.


This particular criticism is fair enough. Before Ada there was PL/1, too.


I wrote Perl for a couple of years early on in my software career. It's mostly write-only. Oh it can be used to write readable and maintainable code, but often isn't.


Cars can be driven safely, but often aren't.

Alcohol can be consumed in moderation, but often isn't.

Parents can raise kids without being emotionally and physically abusive, but often don't.

Marriages can be healthy and stable lifelong commitments, but often aren't.

Education can help raise people out of poverty, but often doesn't.

Governments can provide stability and security for their constituents, but often don't.


Poor analogies: none of what you describe is often the case out of deliberate action. Perl is often written deliberately in a way that is unreadable or maintainable. On purpose. Often because that’s what the language encourages.


Makes me think we need a new language BNW (brave new world) where all the bad things people are doing in existing languages are simply impossible.


The typical Perl program is half as long as it should be to be readable and maintainable.


Is this an indictment of the language or the developer doing clever, terse quackery?


Mostly the latter.

In the rare occasions when I wrote Perl, the language offered all I needed to make my script as boring as Java, along with many temptations to be clever and concise; many people use Perl because it supports write-only "quackery", but it's their choice.


In Perl's case, it's both. Perl encourages it, and "perl practitioners" as a rule tend to revel in it (in my experience).


Oddly enough Portland, Oregon is named for Portland, Maine. If the coin toss had gone the other way it'd be named after Boston.


Which itself has been renamed a few times. Until the British fired incendiary cannonballs to burn it down just before a blizzard. This demonstration of force helped unite the colonists in their support for revolution. When rebuilding, Falmouth became Portland.


In this parallel universe I wonder if Fred Armisen still makes a show but calls it 'Bostonia'. Same number of syllables so the song still works.


Way cheaper than a social media giant.


Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: