skysight-inc/HackerNews huggingface dataset:
Every general election adds at least a few new amendments to the California constitution https://en.wikipedia.org/wiki/Constitution_of_California#Ame...

I could not easily find the comprehensive list. It has to be well over 100. This page, for instance, is only amendments with their own Wikipedia page https://en.wikipedia.org/wiki/Category:Amendments_to_the_Con...
(Disclaimer: I only used the mobile site and haven't registered.)

I second the opinion that these CVs don't look like the academic ones used in the US and most parts of the EU. Perhaps this service is tailored more towards some other part of the world.

I would focus on the UI, examples, and building a strong user base before charging for the service. You could also add biosketches (as required by different funding agencies). If you do an excellent job at it, you might get acquired by services like Researchgate, Mendeley or maybe Overleaf, if you allowed people to import and edit their documents in LaTex.

On the bright side, I would pay for a well-executed SaaS for academic / grant documents management.

Good luck with your project!
How do you know it is your last promotion?
For the most part they already are.

Nigeria has gone from 7 to 5 since 1980, and Ethiopia from 7 to 4. Which is not declining, but certainly progress. India went from 5.5 to 2.2, nearly replacement. Bangladesh went from above 6 to 2.04. The Phillipines in particular shows a dramatic decline from 7.15 in 1960 to 2.58 today.
It's not just the packages. The whole system is as simple and straight forward as it can be. It didn't need many tweaks, and I know everything it's doing. Openbsd just makes me happy :-)

I've stuck with pre-compiled packages, and that's as easy as can be. I've only needed the pkg_info, pkg_add, and pkg_delete commands. There's a syspatch command to pull down OS security updates and upgrade to new releases. After new releases the fw_update command updates any firmware packages, and pkg-add -ui updates all packages. The faq pages have more info on this, and a lot of other system setup stuff [0].

(Extra info: Packages are pre-compiled binaries from the openbsd ports collection [1]. This ports collection can be installed and used to build stuff from source, and more closely track updates. Each app has a sub-dir under the ports directory with a makefile to download source code and compile/install everything to the right place, handle dependencies, etc. Packages are so easy, and I've never needed to get involved with ports. I've used ports on freebsd and can appreciate the value of them, if someone were to need them.)

I don't have much first hand experience with openbsd containers. The system makes use of chroot [2] for daemons like httpd, running executables as a separate user restricted to a specified userland root directory, and I've played with this. There's also vmm [3], which can run openbsd and linux virtual machines. Apparently vmm allows for docker to run on openbsd [4].

[0] https://www.openbsd.org/faq/index.html
[1] https://openports.se/
[2] https://man.openbsd.org/chroot
[3] https://www.openbsd.org/faq/faq16.html
[4] https://medium.com/@dave_voutila/docker-on-openbsd-6-1-curre...
Your product looks great, I’ll give it a try!

I’m curious. What was your thought process when making the decision about open sourcing?

Were you open source from day one?
The recent Bluesky report is hosted on matrix.org

I don't host content on a matrix service but I imagine it's similar to Slack in that reguard.

I could be way off on matrix' utility here as I don't use it for my primary publication.
is it yet an other service-as-a-software-substitution which demands registration and you post your comments and get others' updates via a cerntralized service which easily censors/tracks you? or is it a decentralized solution?
The degree to which I agree with this comment is inversely related to the probability that the author is just joking.
It's not the battery that matters, rather it's whether you get an automatic transfer switch (ATS). Those are more in the $500-1000 range. Of course without a battery that only helps when it's sunny, so you still want a battery. But the battery isn't the safety measure, the ATS is.
The recent Bluesky report is hosted on matrix.org
I don't host content on a matrix service but I imagine it's similar to Slack in that regard.

I could be way off on matrix' utility here as I don't use it for my primary publication.
Many successful databases are open source. MongoDB (at least before the recent license change!) is a good example of a huge company where I doubt anyone would have made a noticeable business out of a proprietary version of the product.
The thing about the Peter Principle is how do you know which is the "last promotion" that you should turn down? No one should turn down the first promotion (from "fresh into the workforce" to "basically competent developer" [or journeyman welder/electrician/plumber or whatever the equivalent is for your field]).

After that it gets murky because everyone has their own abilities and willingness to do what it takes to compensate for their own flaws and take advantage of their strengths.
We are not talking about risk of disaster, we are talking about economic costs. And are are not comparing the cost to other disasters, we are comparing the cost of generating power using nuclear to other methods.
> assuming the idea of increment by one is solid.

Therein lies the rub! Succession is a human concept. All math is a magnificent city built upon that one stone.
He never got any engineering training. The closest he got was a BA in Physics. But yes, he’s a good marketer and his first product is himself.
The problem with documentation is that they're generally written by the developers themselves and are burdened by the curse of knowledge. A lot of bad documentation I've dealt with is often riddled with acronyms and a priori knowledge of underlying systems and external dependencies.

I think a good approach is to hire junior developers/interns and just ask them to build stuff off your API from scratch and carefully record their pain points, questions, etc. As a bonus, the stuff they build can also later be used as working "best practice" examples -- assuming you get your developers to code review them.

I say junior developers because they're a good knowledge baseline to aim for and are probably not "contaminated" with a priori knowledge of your system or similar alternatives.
That’s only half the battle. The working directory is designed to be writable so you either end up with PHP files copied onto the host with some complex syncing that breaks the admin panel, or you accept that the hosts share a common file system.
Reach out to Eugen about that -- afaik he runs the @joinmastodon Twitter account directly or has someone helping him with it, but he's approachable about feedback.
That looks quite interesting, though I was confused when I clicked on the upvotcracy-ui thing and the readme was about something called Sapper. I think your projects could definitely benefit from some brief 'what is this and why should I care' documentation. I'm intrigued by the 'zero moderation' claim but see nothing to explain how that works from a quick look.

While I'm not an investor or entrepreneur myself, there seem to be a lot of promising projects here, if you can refocus slightly articulate the concept to people other than developers. Best of luck.
Holiday towns really should not be considered as lessons to take for good urbanism. Most tourist towns would have their desirable tourism qualities destroyed if they became a land of usually-empty condos like Benidorm.
Got a 9550, hope they fixed them by now...

- I'm through 2 swollen batteries (at least the touch pad coming up gives you a warning...). One the sent me for free after warranty though.

- blew a speaker in week 2

- bluetooth and wifi didn't work together (I now swapped the chip)

- fan blades are very brittle (broke one accidentally when de-dusting and then took out an opposite one so it's correctly weighted)

- these case screws... Super short and mounted at an angle. Easy to screw in in the wrong angle and without lock tight you might loose the before you notice one is coming out.

- gforce card played dead for a few weeks.

- do not use USB-C for power in. Even with a dell branded dock I get system freezes. It's only fine to charge over night or while watching a bit of youtube.

Other than that that it's my daily driver since a few years though and quite alright...

Had another 13" xps at work and the matte version had auto backlight dimming when the screen showed dark content. Super frustrating for dark themes. Had to patch in a leaked fix to remove it (risking a brick) because support wouldn't hand out one.
I think this is a rather oversimplified view of SPACs. Matt Levine recently wrote a nice piece about the magic of SPACs. Here is a paper he cites: https://corpgov.law.harvard.edu/2020/11/19/a-sober-look-at-s...
I do think corps are part of the problem, but not necessarily due to control. Cities are self-reinforcing growth due to the inherent chicken-and-egg problem regarding jobs and companies. Companies don't want to move to the boonies, not enough workers. Workers don't want to move to the boonies, not enough jobs. And everyone wants to be close to universities, because networks, while universities aren't willing to spend resources to move. This was already the case before telecommunication became as advanced as it did in the recent 15 years.

WFH might help break the cycle to some degree, but the majority people will still be in cities (by virtue of, well, being a city), which creates incentives for younger generations to go there (dating + outgoing life), even for those who would rather settle outside the city once they find a partner.
> Many of us are wearing devices with continuous optical heart rate monitors.

I don't know how representative you folks are. I know a few people who invest time, money, and effort into tracking and measuring every aspect of their health. It looks like neuroticism to me. Especially when they look for explainations of every blip on every chart.
From what I've read, spaced repetition like Anki is state of the art for memory intensive subjects like kanji/hanzi.
> why not just let them take the (tiny) initial 8kb hit as an external css file,

One reason is Google will likely ding your Core Web Vitals score for it, which is becoming a ranking signal in May this year (https://developers.google.com/search/blog/2020/11/timing-for...) so you have less of a choice here for what you prioritise.
I quickly pushed up the draft I had locally and will submit an update to App Store, but they have to review it before it goes public. Feedback welcome! https://github.com/oblador/hush/blob/master/PRIVACY.md
Hi

I am the OP. I just discovered that my submission has made it to the front page.

A quick word on the rationale for not using translation.

All of the classic apps (Anki, Duolingo, Memrise, ...) are to some extent translation based. Translating has three scalability issues.

First, if you want to be inclusive and your product to be used by everyone you have to translate the whole product in a long list of languages. I imagine there is a ton of people who do not speak English and would love to learn Japanese !

I don't really know how to express the second limitation better than by saying 'translation is not additive' or it does not 'scale up'. What I mean by that is that if you translate at the word level (such as with Memrise), you learn words but somehow you do no learn the language (to be fair is the point of the app and that works fairly well). However a language expresses itself through sentences and translating a sentence is not the same as translating each one of its word. So you are sort of stuck at the word level and can't scale up to the sentence level by combining the low level components that words are.

Third, translating sentences does not scale well due to the complexity of natural languages. If like Duolingo you base your app on translating sentences you face all the poblem faced by Duolingo.

How do you translate 猿はバナナを食べる ? There are a lot of potential translations. Here are some I can think of right now :

The monkey eats the banana.

The monkeys eat the banana

The monkey will eat the bananas.

The monkeys are going to eat the bananas.
This is nice to see. I’ve played around with Chez and Racket separately, and even though I’m now focusing on bare metal/JIT again, I look forward to using the new Racket.
> How would you have handled the string/bytes split in a way that’s backwards compatible? Or the removal of old-style classes?

I'm not sure it's the best way to handle it, but I would have been fine with:

from __python2__ import *

for full backward compatibility; or, more explicitly:

from __python2__ import ascii_strings, old_style_classes, print_statement, ...

As the parent poster mentions, several other popular languages and systems (C++, Java, etc.) have done a pretty decent job preserving backward compatibility, for good reason: it saves millions of hours of human effort. It's embarrassing and disappointing that Python simply blew it with the Python 2 to 3 transition.

Maybe we could still evolve pypi to support a compatibility layer to allow easy mixing of python2 and python3 code, but I get the feeling that Python 3 has poisoned the well.
The problem with "signalling" theories is that they can explain nearly anything. Why did you do X? Why, to show other people that you are the sort of person who does X. Even if you didn't know it at the time.

It's hard to see how you would go about falsifying it. It's way too convenient as an explanation for whatever you want. It's less a theory and more a very particular lens to view the world through. Nearly anything can be slotted into it.
In poorer nations autonomous cars could take much longer for mass adoption due to different, sometimes harsher road conditions, and lack of reliable road-map data.

In addition, self-driving vehicles would be pricier. For a poor nation, that price tag might be higher than human labor.
The US military issues medical waivers for these things. It was very common for African-American males (and some others who have justification) to be on a medical waivers (simply referree to as shaving waivers) to not shave when I served. It's not really an issue, or at least it wasn't 20 years ago.

It seems the USAF is now issuing these waivers with 5 year terms. [0].

[0]: https://www.airforcetimes.com/news/your-air-force/2020/06/24...
Sure, but I think your example of a neo-Nazi vs. non-Nazi meeting up in a room describes a minority, extreme case. Most people are not Nazis, and most of the bad discourse on the internet does not involve Nazis.

Two somewhat-reasonable people, even if they're complete strangers, could have a productive discussion (or at least resolve to agree to disagree, if it gets a little heated) if they were to meet in person to hash things out. But in an online conversation, especially on a limited medium like Twitter or Mastodon, they could both easily devolve into talking past each other, name-calling, and arguing in bad faith.
Alabama never updated parts of their constitution to remove it as they kept losing federal court cases. It just became unenforceable.

For example their constitution still contains language for school segregation and removing voting rights for interracial marriages.

Even when they did make updates. It was in the form of amendments which increase the overall length. Eg, the amendment that lets women vote.
I envisioned a floppy-shaped USB drive that can be inserted into a 3.5" drive.
To me it sounds like all cards are on the table, as opposed to reverse mergers.
Just on a technical note: With interest rate r, an infinite stream of annual payments P (aka a perpetuity) is worth P/r. So, with rates around 2%, the cost of security forever is the annual cost times 50.

(I guess what you're saying is that rates are effectively zero, and they are, and then the cost is infinite indeed...)
You should seek a really good therapist, you're far too young to be 'over it' already.

You can live an authentic life, you just don't know how because 1, you're a kid with zero wisdom and 2, you don't yet know what is important (related to point 1).
In theory that’s true but in practice there needs to be a common file system for WP to function properly otherwise you end up with a lot of kludges that break the admin panel or that adds other caveats to WPs normal behaviour.
Not buying the storyline. Certainly Tesla will have to keep upgrading its systems to achieve true FSD. They could even decide that LIDAR has become cheap enough to use anyway. What they have is cars on the road collecting data. They'll have to collect new data and develop new algorithms on that data but that path is not excluded from them.

> "It is a misconception that you can just keep developing a driver assistance system until one day you can magically leap to a fully autonomous driving system," Krafcik said. "In terms of robustness and accuracy, for example, our sensors are orders of magnitude better than what we see on the road from other manufacturers."

Not a good argument, very handwavy. Better sensors is not a moat. What is your software, how is it qualitatively superior? No one suspected that NNs or even DNNs could produce AlphaGo/AlphaZero until it did.

Until Waymo gives their tech to the public and we can compare how well their less used but superior hardware and software performs it's all opinions and PR.
If you want a linux machine, I would strongly suggest going with https://system76.com/ rather than getting a thinkpad or dell or whatever, if one of their options work for you.

The main thing I dislike about them is too many of their laptops come with 10-keys on the keyboard, with no option to not have it.

If you're not sure if you want a linux machine or not, I can't really comment since you know better than me how much this matters.
Interesting. Spacex says it's 5 years for the 550km orbit without propulsion. Maybe the orbit isn't perfectly circular or something else changes the maths.

wiki citation - https://spacenews.com/starlink-failures-highlight-space-sust...
you da real MVP
That people can make an initial plan that is self-consistent, logical, and foresees and provides for all future use-cases is a basic tenet of waterfall-style development. The history of software engineering does not uphold that principle. Why would it be different for language designers?
#21e8
As someone that semi-regularly follows this blog, that is pretty much the the full one.

It's pretty simplistic in its design.
Interestingly enough, the opposite trend can also be observed. https://www.wsj.com/articles/SB113236377590902105

"I don't want my child to be in an overly competitive environment."
One method is spending money on sensors, the other is on gathering as much data as possible (cheaper sensors, but put in all cars).

In 20 years we'll probably have good enough algorithms that can work with few data and cheap sensors, so it's just a matter of time until the 2 methods converge.
why? what? why not support like 10.12 11+ only, what was the super cool toolkit you needed for this app to cut off people on like not that old laptops that can't update.
I have a fairly similar hackable script in my tools repo on GitHub for the curious.

Essentially I wanted to be able to pipe the music I was playing into the stream and the microphone input.

Also I wanted to allow for a secondary camera (droidcam for me) at leisure.

I suppose OBS is better if you spend the time with it.

https://github.com/kristopolous/tools/blob/master/bin/screen...

There's a preferences file example here
https://github.com/kristopolous/tools/blob/master/bin/.scree...
Well yes if we put grossly misleading numbers it would be even worse of a sin. What I mean is that it is not a system cost. This assumes the existence of dispatchable low carbon energy at large scale without acknowledging this cost. You can't meaningfully talk about $/kWh with solar in the context of deep decarbonization without talking about the cost of dispatchable duplicate backup capacity. Costs and success today are riding on the back of a huge and high carbon dispatchable grid.
Michael O' Church has written some amazing blog posts. If you tolerate his style, I highly recommend reading him.

Too bad he fell out of grace from the SV elite (and I can totally see why). I wish he continued writing as much as he was back in the time.
For me, the reason I would have more than one format of CV is for grant applications. Every so often, I need an NIH or NSF biosketch, list my current support, etc. I see nothing here indicating this supports those agencies, just a set of templates without any indication of why I need a lot of different templates.

ven though I say it would be useful for grant applications if you had those templates, you will be competing with the government for that use case, NIH created SciENCv, which will generate your NIH and NSF biosketches from a single source of data.

https://www.ncbi.nlm.nih.gov/books/NBK154494/
I don't think the author really understands the characterization of Michael Scott. I can't imagine the hypothetical scene of Michael Scott taking pride in knowing how to use chopsticks. That sounds way more out of character to me than having him not know how to use them. Hard for me to take the article seriously when it has to make up character traits for Michael Scott to make its point.

I believe that the type of person the author thinks Michael Scott is exists and sucks (and I'm probably one of them), but I don't think Michael Scott is one of them.
Search index use cases probably also benefit from normalizing inputs across encodings, that's no shining example of utf-8-onlyism.

You can still best-effort split words! You can do a pretty good job splitting words without ensuring that the words decode in your preferred encoding.
Only because developers absolutely insist on building things that way, for some reason I will never comprehend.

What's the first thing most people do when starting a new project? They ask "what framework should I build this on?" and start their tiny portfolio site built upon a massively overpowered suite of enterprise-level software with a million features they'll never, ever need.

Then they might drop in ten or fifteen separate external libraries because using vanilla HTML, CSS, and JavaScript is just "so 1995".

Then they start thinking about AJAX and microservices because rendering an entire page on the server side is utterly unthinkable in 2021.

Then they cram the site full of third-party services (because your tiny home-brew website will definitely benefit from Newrelic monitoring).

Then they might start on unit testing.

Finally they package everything up using at least seven different dependency managers, because a Github project without 100 useless ancillary files (grunt.js, app.yaml, travis.yml, composer.json, .gitignore, etc. etc.) is obviously not acceptable.

And this is why I hate modern web development.
Local timelines are at best an attempt to help with content discovery and really too overrated. If the instance is too big, it feels like reading from the firehose and if the instance is too small it is better to just browse the directory and find the profiles that seem interesting to you.

To me local timelines only make sense if the instance has a very clearly defined group with some kind of shared access, e.g, a company that has an instance for use by its employees, or a club or organization have some kind of membership. Unfortunately Mastodon's culture seems to about aggregating around instances with a very loose sense of "community" - e.g, "photographers", "open source developers", "lgbtq allies". To me this is - quite frankly - stupid. Not a day goes by on /r/mastodon where someone asks "is there an instance for X?" thinking that Mastodon instances works like subreddits.