skysight-inc/HackerNews huggingface dataset:
You forgot that it is satisfying. I moved to a spiral wipe notebook and find I can sketch and write notes much faster before dragging yet another box, look for text label, etc. Which usually results in losing the fleeting thought.
hey im new im a hacker i say we party for friday
Thanks, but that's what was in the article.

Why is this better than monorepo, specifically? What use cases does it allow that aren't possible in a monorepo?

BTW, the typically talked about giant monorepos do support branching, and the branch is never the entire repo.
I agree it is benign. There are only a few Bill Gates level rich people donating buildings. Sure it is corrupt strictly speaking but would you rather a poor student compete with one Gates kid or 100 millionaire kids that have discovered other cheaper corrupt openings?
It usually helps to have a systematic mathematical model for the problem you are trying to solve, and systematic mathematical models for the sub-problems into which the full problem is decomposed. It is frequently better to conceive of each step in the program as ensuring some property is invariant rather than conceiving each step as performing some action.

It is probably better not to think of yourself as a coder or a programmer; consider yourself a problem solver with mathematical skills and move on to there.

Always convince yourself that the problem you are trying to solve has a solution.
If it’s an issue with newer devices, just don’t show it for newer devices.

Or, since it’s a self serve platform, let the author decide not to show it to new devices.

Delisting seems rather extreme to me.
You may be over complicating things. Or maybe I'm oversimplifying.

For us, it's pretty simple to talk about our product because we're helping improve sleep. It's such a common problem in today's society, and the existing "solutions", focus on comfort, other physiological changes (cool pads, weighted blankets), ear plugs, eye masks, etc etc. We're using neuro-feedback to alter your sleep state. It's pretty magical. If you want to find out more, check out https://soundmind.co

So, we talk to people and not only about their sleep, but about how it affects their life, what do they do about it, what do they try, what works for them, what doesn't. From here, we were able to build comprehensive user personas, and those personas describe where our users are.

It was also super interesting for us to find that almost nobody talks to their doctors about sleep, very few people we spoke to had been to a sleep lab+.

When you say there are 100s of target segments, yes, you're right, but you don't care about those. I think you care about two things.

1) can you create a customer persona or two, which are large enough to be viable to get the business started

2) is there a common thing that they do, or place where they congregate to reach them?

Don't make a checklist of all the places they could be or all the possible segments, just talk to people, and look for the commonality, let them self-suggest.

That's my 2 cents anyway.
The Etiquette School for China's Super-Rich
Pascal/Delphi do not use regular object files, instead they have DPU/TPU files which both contain parsed headers and object code.

Those files are not compatible between major versions, so this probably means they are designed to make them as easy to parse as possible, and map closely to internal compiler structures. This means including a unit is way faster than re-parsing the unit's text.

Additional speculation: those DPU files might contain a copy of relevant definition (like names of fields, sizes and offsets). This means if you have "program" which uses "my_unit" which uses "high_level_comms" which uses "Handle" defined in "low_level_comms", then definition of "Handle" could be copied directly into my_unit.DPU. So when you compile "program", and it includes "my_unit", all you need to read is "my_unit.DPU". You do not care about total size of "high_level_comms" and "low_level_comms" files.

Unfortunately, in C/C++, when people '#include <iostream>', they can now use "std::plus", "mbrtowc" and "timer_getoverrun". Which means including high-level modules has to bring tens of thousands of lines in translation units.
(Yes, impl pattern, well-designed interfaces, forward declarations can fix this, but few people bother. Stdlib certainly does not)
How on earth does anything in the current discussion point to "SV eating itself"?
As far as I can see they didn’t ask Telegram to take down the channels. Just the individual doxing messages.

As for ‘doxing the oppressors’, three law enforcement officers were indivually targeted. Sure they are part of an oppressive system, but so are many other people.
RISC OS is written mostly in ARM assembly, but it's a pretty complete (if dated) OS. I think it would be interesting to convert the sources to LLVM-IR and then abstract the hardware specific parts giving you a cross platform version of RISC-OS. Yeah, it'd be a lot of work ... but I think it'd be very cool.

Why?

25 years ago there were dozens of OS's: AIX, Ultrix/OSF-1/Tru64, HP/UX, DG/UX, SCO (yuck), MS-DOS, Dynix/PTX, Solaris/SunOS, Windows, MSDOS, Mac, VMS, RISC-OS, Amiga, BeOS etc. etc. Now we're down to a handful of OSs with a large amount of computing now converging on Intel/Linux -- FWIW, I have nothing against Linux, I've used it since the early Slackware / pre 1.0 kernel days.

But I do believe competition is a good thing and the current trend for OS (and processor) convergence is worrying to me. I'd like to see more innovation and diversity in this space.
Surprised to see GPSLogger here on Hacker News. I've been using it for 8 years now, basically ever since it's been possible to track location on a phone all day without recharging. This app is a gem.

Besides Google Location History / Google Timeline, GPSLogger is pretty much the only way to have records of your location. I've used it for research (we mention it in an academic paper on location-based memories), for my own records to see where I've been (like "how many times have I been to this area before"), and statistical analysis of my everyday habits. If you want long-term location history, GPSLogger is probably the only way to do this.

The alternate, Google Location History, has only been really reliable for the past few years, whereas there was a long period when GPSLogger beat it hands down in terms of accuracy because it would do GPS with cell tower fallback, which is probably the best setup in terms of battery-accuracy tradeoff. The author implemented this in 2013 (it was an issue I filed [0]), and combined with the configurability of when it should try to get your coordinates, you can get long/lat records for almost no battery. If you want to own your own data, and export data automatically, GPSLogger is also the only way since Google doesn't let you automate data export as far as I know (plus if they did, you'd have to rewrite that code every year). My instance of this app has run in the background, syncing data hourly for months without needing a restart.

GPSLogger is one of the reasons I stick with Android. I'll keep using it even if I have to sideload the APK. It's really sad that the author has had to go through all this stress. But it's also worth noting there isn't a way to collect location records on iPhone at all, or sideload an app (ipa/apk), so Android is still the more open of the two platforms. The buffet of apps that used to do this type of location tracking (Moves, Gyroscope, Foursquare, and a bunch of indie apps) are basically all gone or pivoted away.

I'm disappointed that there's such a mindset here that apps should have subscriptions / revenue to be worth maintaining. Freeware and "indie" open source supports the long tail of usage. The popular apps can only get to 80% of the use cases out there. This also shows the inadvertent double-edged sword of privacy/security of indie apps, as they often use more hack-ey techniques which are the first to get blocked out. The most private/secure app is one that does nothing more than a website.

[0] https://github.com/mendhak/gpslogger/issues/184
Historial note: To avoid sqrt, the Atari baseball cartridge went the 1897 Indiana legislature one better, using octagons as circles.

π ~= 3,314?

Unte im finyish du kaxa okwa bik, 4 600 mm bi wit dek xante im. Na desh kuwang, unte im 2 300 mm gova bik, unte 14 000 mm fo imim du gang im.
- 1 Da Bosmang Da Bik Imalowda 7:23
It is much more efficient these days. They use apps to determine when to stock, how much to stock ect. They need many fewer people, and they run much leaner.

Like I mentioned in a comment above, who we consider made it happen is arbitrary. Walmart cannot exist without a functioning society. The daughter of Sam Walton never worked at Walmart, yet she gets more of that gain than any other individual.

For other products, it is even more arbitrary who gets the benefits. If facebook disappeared, another company would quickly take the role of social media leader. Likely not much would change from a productivity standpoint. Yet whoever happens to get the role of dominant social media ceo makes billions.
> It's not at all new. Ever heard the conspiracy theory that Menthol cigarettes cause infertility to target certain demographics? I remember this wild theory being widely propagated long before social media even existed, among other ridiculous conspiracy theories. The idea that the moon landing is false is as old as the moon landing itself. This is not a new phenomena.

Whether the phenomenon being new or not is beside the point. The concern is that conspiracy theories are spreading more than they were in the past, and that groups have learned to exploit the them to accomplish their goals.

This has a parallel to what happened with computer malware. It's existed for about as long as home computers have, but up until 2000 or so, the bulk of it was merely childish pranks and wasn't very concerning. Since then, it's exploded in volume and danger, as criminals realized it could be used to make money by sending spam, stealing passwords and payment info, or by holding data ransom. I remember getting a virus on a floppy disk when I was a kid, but that doesn't make me comfortable with getting contemporary malware on my computer.
I have a degree in electronic systems engineering. At college I learned about both digital and analog circuit design and fabrication. Had my fair share of FPGA and Assembly programming. Built some microcontrolled printed circuit boards. In summary, I believe I have a reasonable understanding of how computers work underneath, and I'm not interested in using anything other than a high level programming language for consumer application development as well ;)
Perhaps it works for some people but handwriting was always slow and painful for me. I tried a bunch of different pens, grips, and writing styles. Nothing really worked. Hated writing and note taking in school when I couldn't use a computer. Now fortunately I can avoid it almost entirely.
Edit: just learned about OffsetArrays.jl - ok now that's really cool. Keeping comment for context.

> - Arrays start at one

Oof. Big turnoff for me. For some reason, this particular context switch really grinds my gears. All languages I use (except bash, which grinds my gears) use Dijkstra-style array slices: python, go, c/++, js. I'm sure it makes it easier for Matlab converts.

This, plus the mentioned weaknesses with libs like http, grpc et al, IMHO will relegate Julia to many years of just being wrapped by other languages. To avoid that, I think they should be thinking about continuing to woo more of the engineering crowd - which to their credit I think they've done pretty well so far.

https://www.cs.utexas.edu/users/EWD/transcriptions/EWD08xx/E...

https://github.com/JuliaArrays/OffsetArrays.jl
Even after knowing assembly, there's probably significant optimizations that can be done if you design chips and ISAs that are specific to a certain problem. There's "waste" at every stage of abstraction.
U.S. Cyber Command Behind Trickbot Tricks
Yeah not sure why he would worry about people using old devices if the old versions work fine. Just drop that code out of new releases and don't support old devices. It's not like the code will bit rot. Getting pulled from the store though that really stinks and google should be more transparent about that.
Back when I was in electronics during our Digital circuits section we built all the logic from gates and such (TTL, CMOS) and then at the end we learned 8085 assembly using an "Emac 8085 primer trainer" which we all had to build ourselves. It had no battery backup (optional) and we were not using the serial output at all...so we lost any programs we made on power off. It was very interesting to learn and I feel fortunate that I understand computers on that level.

That being said...I don't really do code at all :) Most of what I do is on the hardware side of things.

Edit: Emac...not emacs
I don't see how it's false given that the only way to do it is to restrict access to those channels on iOS. I still see no difference. "Because your app on our platform we will censor whatever people do in it"
You can also open Youtube URLs in VLC. Haven't tested the performance on a pi though.
From your most recent blog:

> any individual's reputation, perspectives, and history are difficult to ascertain, and therefore their words must be taken at face value. Coupled with an almost complete lack of standards for participation in the community

Let me translate that out of new-speak: "On the internet no one cares about my credentials (or is afraid of my power) so I must defend my positions on their own merits which I can't do, so we should ban people from the internet who express opinions I don't like."

Would Hitler disagree?
In 1986, after quitting my PhD in computation molecular biology and starting out on a career as a software developer, I tried to figure out what the goal for the next 5 years was. I settled on satisfying myself that I understood (enough about) every level of the computer from semiconductor physics up to GUI/UX work. Luckily I had the semiconductor stuff already covered from my undergrad days and a friend from that time who was an EE major.

The rest took a bit longer than 5 years (maybe 7), and of course the learning didn't stop there. But I do remember thinking in the early 1990s "OK, I understand the entire stack at this point, what comes next?" My understanding had reached a level I was satisfied with - it would not have compared with someone who spent their entire working life focused on that level, but it was far, far beyond any normal computer user's understanding.

In the 2 decades and more since then, not a whole lot has changed that has invalidated the understanding I think I gained at the beginning. Microcode was a bit of a shock. The biggest shock has been watching a whole new generation of programmers who barely grasp the lower 80-90% of the system. Maybe that's good, but it doesn't feel obviously right.
Because the money earned vs old devices probably isn't worth it. At some point you have to cut support on old stuff unless there is some financial pay off or you're retired and want a hobby to keep you busy.
I think the problem is actually the opposite. There aren't enough abstractions that help programmers write good code. So when a programmer has to do something complex, they end up doing the easy thing which is just importing every library they need. If instead, there was a way to say "only import this when I'm doing this action" and there's no way for the programmer to explicitly say what to import, then that problem almost disappears.
Really happy for the team. Huge fan of Segment from the start, and Twilio is slowly getting itself into the middle of everything. (I realized only recently that they've owned Authy for years following the recent rebranding.)

I find it interesting that Segment (and thus the entire downstream ecosystem) has gone this far while staying strictly oriented around users and accounts, without first-class support for other entities -- namely a notion of workspace/team/contract/opportunity/etc. "Groups" was sort of a false start that didn't get a new direction. There's still a ways to go connecting all the dots between how companies structure their data and how all third-party products are prepared (or not) to mirror that structure.
Village Foods Traditonal Diya Habarala Recipe Sri Lanka Wel Habarala Pond Weed
Can you give even a single example of:

- a significant (eg, at least as complex as wget) software project,

- that has been unmaintained (no updates, code has the same MD5/etc hash),

- with a significant userbase (not sure exactly how to define that one),

- for a significant amount of time (at least five years),

- which is generally regarded as finished and bug-free (not in need of further development) rather than abandoned?

Because I can't think of a single one, and the only ones that even come close are video games where the known bugs were co-opted into gameplay features. The general consensus seems to be that any system that doesn't have automatic updates running is de-facto insecure (which, since every update mechanism I've heard of can introduce new code (ie new security vulnerabilities), means any system whatsoever is insecure).

(I don't quite disagree with the tacit assertion that actually getting things right on - if not the first try - then at least one of the first thirty or so is a extremely, maybe even unreasonably high standard, but it manifestly is a standard that basically all existing nontrivial software projects fail to meet.)
> I guess this has been solved by include guards/pragma once a long time ago

include guards don't really solve this problem, because the preprocess needs to read every line to find the end of the include guard. The pragma once solution works, but it is hard to implement it for every system (what happens when a file has different names but same content)?
As someone who has been coding for 20 years, "magic" is a negative adjective for me. I don't want magic code. I want code that is simple and works in obvious ways.

> You can even specify a version number

Sorry to be sarcastic here but wow, you mean I can even make sure that my code will not break at an arbitrary point in the future, when my dependency inevitably introduces a breaking change? Fantastic.

I understand that installing dependencies is a bit of a hassle. But really, once you have done it twice it takes seconds. And I would not want a mechanism that fetches dependencies as a side effect of my app running. I want to know what's going on when my app runs. The fewer moving parts, the better. Often, it's hard work to achieve this simplicity. But, at least in my experience, it pays off.
> Someone stocking shelves in 2020 is about productive as someone stocking shelves in 1968.

Note there was an article on the HN front page just in the past week or so about how Amazon warehouse workers were getting more repetitive stress injuries because partial warehouse automation allowed them to fulfill 3x the number of items per hour than before these systems were put in place.
But if you google "twitter bots state level actor" the first three links are two government sites and one is nature.com (as in the big journal Nature).

I can give lots of examples of googling that gets you to conspiracy sites, but I am not sure how those examples would prove anything...
When I read this I did an image search for "hot onions". I had no idea! Cooking has changed a lot in the last 20 years.
People generally pay for products in order to get a benefit. It's still genuine.

The difference is the seller gets to share some of the benefit.
I find myself in the need of a "lib_download" a few times, a high level library that:

- support HTTP/HTTPS

- support proxy (for by-passing firewall, censorship, etc, http/https/socks5)

- download one large file in parallel (configurable temporary directory)

- download many small files in parallel (seems too high-level to put in a library, not sure this is a good feature)

- configurable retry (maybe too high-level to put in a library)

- resume download

- good error semantics

- an interface with defined behaviour

- progress report (useful for downloading large files)

I tried using a wrapped (in rust) version of libcurl, and in the end I decided to just use the curl cli, and read through the man page and pass about 13 arguments to it to make it's behaviour defined (to me, to a certain confidence level), I also pinned the curl executable to a specific version to avoid unknown changes.

The end result works, but the process is unnecessarily complicated (invoke the cli binary, know what argument to pass, know the meaning of the many error codes), and the resume is not pleasant to use. I guess libcurl is designed to be that way, so that to an curl-master, he can tune all the knobs to do what he want, but to a average library user who just want to download things, it requires more attention than I'm willing to give to.

Used in an interactive context, the issue of defined behaviour is usually overlooked, but when used a library in a program that runs unattended and expensive to upgrade/repair, achievable defined behaviour is a must, and test is not an alternative to it, even experience is not an alternative (experience are time consuming to get, and not transferable to others).

All package managers needs to download packages from internet, often via HTTP, it's good to have a easy-to-use, well-defined, capable download library, many of them uses curl (Archlinux's pacman, rust installation script), many of them use others with varying level of capabilities, I thinks it would be beneficial if we can have a good library (in rust) for download things.
Here’s the original post [1] and another early thread [2]. Always fun looking back with 20/20 hindsight.

[1]: https://news.ycombinator.com/item?id=4912076 "Analytics.js"

[2]: https://news.ycombinator.com/item?id=5116832 "Segment.io"
The app store ecosystem clearly has value, and I think Apple are entitled to make a profit off of it. (See, for example, comments below about how difficult it is to cancel subscriptions to other kinds of services.) The problem is that the 30% Apple charges has no relationship whatsoever to the amount of value that the app store provides - it's simply how much Apple can get away with charging. If alternate app stores were allowed, or alternate payment mechanisms were allowed, Apple would only be able to afford to charge a premium commensurate with how much "better" their experience is.
No! The supply-demand curve intersects at $100 and not $70. 70/30 split is an internal transaction and cost of doing business. No different than distributor cut if you’re selling physical products.

The customer paid $100. That is by definition the price. All costs are relative to the price. For example, sales tax or transaction fees.
> It should be 10%? 20? 5%? What will be an acceptable %? Who decides that? What's the framework for deciding that?

The framework is called competition. If Apple's IAP billing or the whole app store in general faced any competition on iOS they wouldn't be able to charge anywhere close to 30%.

But Apple designed their platform specifically to prevent that, to retain a tight grip over app distribution and billing.

> I see one solution, and it's far fetched, developers/companies should fund and push for an alternative open platform, along with phone/device makers.

Good solution, but we won't get to it. The moat of Apple-Google mobile duopoly is way too massive to overcome naturally at this point. We need some regulation to reign this in. Mobile computing is just as essential as telephony and internet access. We can't have two companies dictating the rules of the game for the whole economy.
Practical experience with AWS RDS postgres is that an m4.large instance chokes at 150 connections. We are currently planning to test RDSProxy, but does anyone have experience with comparing this service to running pgBouncer ourselves?
These are yellow onions. Someone has a fetish.