skysight-inc/HackerNews huggingface dataset:
skype was good before microsoft took over :/ I wish they'd rollback the interface. It's really annoying how I can't tweak anything anymore, I used to sabotage it for the memory it uses. Now my PC is too slow to do much if I have it running in the background.
The horror. I actually had a dev tell me he didn't trust doctrine (symfony project), so would do it all in SQL. Thankfully the project was relatively new so it was possible to rewrite everything using migrations.
Just to add to this point, I wanted to implement JMAP after only half completing an IMAP server implementation. Unfortunately, its just as bad only "this time with HTTP and Json". The batching advantages of JMAP could be generically done by using HTTP 2 and/or GraphQL.
It's called a high-trust society. It is the gift granted to you by your forebearers.

Use it wisely, and preserve it for those after you please.
And betting those profits come in the process. Huge difference.
It’s funny, I feel the same way about web development right now.
Went keto, depression went away within a week. Switch to carnivore for financial reasons, anxiety went away.
we have had good success with liquibase[0] and flyway[1].

[1] http://www.liquibase.org/
[2] https://flywaydb.org/
Maybe you just care too much. I trim my beard whenever my wife complains (once a month maybe). Takes about 10 minutes and that includes scissors to get the stray hairs and moustache.
that's also my first impression of this article. but i (hope) believe google is aware of this security concern, otherwise they'll probably be the next Microsoft
This indeed seems to be the main issue (which LetsEncrypt didn't need to worry about). Zero cost would necessarily mean that early users will hoard all the valuable names, leading us back to square one.

Human-recognizable names are a scarce commodity. Zero price would create a market distortion.
jfrog's artifactory has nice support for python https://www.jfrog.com/confluence/display/RTF/PyPI+Repositori...
Usually, in my experience, you submit a pull request, add commits to fix things in the request, then when everything is copacetic, you squash the commits and submit a final pull request. You have to do a push -f to make that last request.
I'm not sure I understand the point of this article except to write a hit piece against Howard Schultz. For shame, NYTimes.

Schultz is no longer the CEO of the company and it is easy for Starbucks to distance themselves from his campaign. A simple press release: "Howard was a great founder and we wish him well in his future endeavors".

Additionally, media should refer to him as: "Howard Schultz, the former CEO of Starbucks." That makes it clear that the two are no longer affiliated.
Perhaps Edge. A recent version.
Pizza Reviews Are Meaner Than Video Game User Reviews: A Definitive Comparison
It's not the project that asks people to push fixups, it's that GitHub, as opposed to e.g. Gerrit, makes it hard to see what changed (how your comments were addressed) after a force push, so it's best that people only add commits.

Ideally they'd use git commit --fixup=<sha> -p, and then git rebase --autosquash when the maintainer approves the merge, but few people care.

(And what I'm saying isn't really accurate any more since GitHub does show force-pushes in the pull request UI these days and one can run git range-diff on that. But this wasn't possible last year.)
Basically because it's all just github, the package author and publisher are intrinsically linked because the package repo is directly associated with the code repo. In NPM, there is not any way to directly ensure the publisher and package author are the same because they're different systems.
Straight razors are very cool and a bit intimidating, but for me personally the maintenance makes it a non-starter.
The Changelog 345: Quirk and Cognitive Behavioral Therapy (CBT)
This is bullshit. It's absolutely necessary for the user to be able to refer to the resource by an ID of some sort. A slug is not an ID.
Prepare for the exciting future of DevOps transformation: it's `./manage.py makemigrations`.
It seems to me like there's a potentially privacy sensitive way to share the information. For any role with more than N employees, the mean and standard deviation are published: simple, equitable, and private.
> No, it's not. If anything there is a belief that DE blades actually stay sharp and last longer than cartridge blades.

I find this hard to believe. I can use a single Gillette Fusion 5 cartridge for a month or more.
What was the relative scale of the two systems?
How to Accept Payments on Your Website (Easiest Way)
The government of Ontario releases the salaries of all public employees every year if they make over 100k. So called sunshine list https://www.ontario.ca/page/public-sector-salary-disclosure
Most of India is suffering under extremely high levels of particulate pollution - I wonder how this is going to start affecting the population there, especially as life expectancy is increasing.
It was still an IPO, just an untraditional one.
Which citations are you referring to? I would be grateful if you could please be specific.
Skype in the business since 2003

Telegram, Slack, Google Hangout are much younger and still, they win Skype in every aspect.

Microsoft needs to wake up or Skype will join ICQ
Or just replace them with normal links (or iframes, depending on the user setting).
Looks ghetto like most Linux UI, needs more padding
> Chrome on desktop has between 60 and 70, and afaik less on mobile, and less in the US. So, no.

No, it has about 60% on both mobile and desktop, not counting the derivatives (like Edge and Opera). Considering that both of those markets grew significantly since IE6 days, that makes Chrome more dominant than IE ever was.

And you seem to assume that an average consumer installs stuff on his own after the OS installation, which is not the case with less tech-savvy people I know. They usually give it to someone a bit more tech-savvy to do post-install tasks, and those always include an installation of a different browser. Every single second-hand computer available in my country's market comes with a cracked version of Windows, MS Office and a different browser. Tech-savvy ones just reinstall the OS, non-tech-savvy ones continue using the defaults — the defaults set up by someone else.
If/when they add a build service (like Bitbucket Pipelines), they have a golden opportunity to provide a strong guarantee that a package was built from a particular Git commit (i.e. the source code wasn't modified to add malicious code). That would make me feel a lot better about using pre-built packages.
Report case of a Nigeria who infects their country with Monkey pox – Onyi News
Don't really see how any of this doesn't apply to the world today. The rough range of your salary is pretty discernible by your job title in the vast majority of cases. If you're a Senior VP at Amazon for the past 5 years the world already knows you're loaded.
There's already a huge database of your coworkers' salaries, assuming you work with any H-1B visa holders (https://h1bsalary.online). I seem to recall the government had a portal you can search by name too.
It depends on who you’re telling. People treat you differently when they find out how much money you make, both on the upper and lower ends.
Is there a measure of this? if you wanted to keep a price at a certain level, obviously you could buy endlessly at a current price while people sell at that price until you own everything.

But let’s also assume some large proportion of players are reactionary, tending to sell when the price drops and buy more when the price rises. If you could show a sufficient demand at price A, then that large block of people would not sell their holdings because the price does not decline beyond A.

Then, the economically rational actors have a dilemma because they believe the price should be B (where B < A), but powerful actors have shown it is unlikely to drop below A for all practical transaction volumes... it may make more sense to treat the true price as A.

I guess what I’m asking is how much money relative to market cap is required to make the market accept an inflated price _without_ actually trading on it and losing money?
To anyone reading this: if this happens to you, please talk to a lawyer. Please do something to protect future tenants, get the landlord's info online. Don't seek retribution just for yourself.
Perhaps the strongest argument against is basically that if you're the only one telling, you are at a disadvantage. It's a prisoner's dilemma.

By comparison, in the public sector & military, everyone's is public, and on top of that there is no salary negotiation.
[ Male baby boomers aged 55 to 64 like “Solitaire” and “Scrabble”, while women lean towards “Mahjong” and “Monopoly.” ]

No wonder I don't play games with my computer! What an awful selection!
> How do you verify that?

I think if they required a user or org-namespaced package name, you'd get that. For example, if https://exiftool-vendored.js.org was `@mceachen/exiftool-vendored`, or `@photostructure/exiftool-vendored`, it's explicit, in the package name, who you're trusting.

> ... did someone get unauthorized access ...

If they required publishing to be via 2FA-authenticated users, and (if I can dream), GPG-signed commits, I think you get most of the way there.

Github is starting greenfield here, and it's frustrating they didn't (at least afaict) require these small steps.

When I'm looking at a given package, I'd like:

1. Assurance that the package was published by the author
2. Assurance that the package contents were generated, in an externally repeatable way, from a release tag.

It seems like they could have lifted 1. by requiring 2FA and GPG.

It seems like their new Actions tab could have given us 2. It may, I can't tell from the demo.

And when I update my dependencies, I also want to see the diffs from the version I'm updating from. Github already has nice comparison views for arbitrary commit shas, so this should be doable as well.
Git is a complex system, of necessity, and rebase is a flexible, powerful tool. Some of the things it can do are common parts of the normal work flow. Others are only for serious situations.

I generally prefer transparent systems to those that try to figure out what I really want to do.
> Java has a big selection of GCs, and each has their bunch of knobs for tuning. And you have to pay attention to that stuff.

You never have to touch them in the Java world either, unless you like making performance worse that is.

I've never ever seen a case where fiddling with garbage collection parameters didn't make things slower.

I worked with a guy who worked on a popular java compiler, and he says the same thing. he never twiddles GC parameters either.
Sphinx chamber at Emperor Nero's Roman palace brought to light after 2k years
Maybe because PyPI has a closer relationship with Python than the other package managers have with their core tech?
Tuning GC is hard, and the nondeterminism is worrisome, but hitting a pathological case and rewriting a bunch of code hoping to avoid it is even harder.
No. They are both typed languages but the feature set is not even comparable. Swift is a huge language
To host a private Python package repository, I create a simple directory tree where the first level is the package name and the second level is the package (a tarball, zip, or a wheel) and I serve that tree over HTTPS using vanilla Apache or nginx with directory listings enabled. Then I use "bin/pip -i https://packages.example.com ..." to point to that repository. It's very low tech and it turns out that's all I need.

Whenever pip can't find a package due to case or hyphen issues, I look at the access log, find out what pip is trying to retrieve, and rename things or use symlinks to fix it. Also, I manage the directory using git. (One of these days I'll try using git-annex or similar, but for now, a few gigabytes is not even close to being a burden.)
would be funny if Google would code for somebody else's problems
The investors own the business. Why would they be worried about the business and not just what is in their own best interest.
> And your skin will never be irritated

I develop dandruff under facial hair, just like the top of my head.
i found more info here, hope it helps: https://blog.ltse.com/how-ltse-will-and-will-not-be-like-oth...
https://www.dropwizard.io/

Quoting from the site: Dropwizard is a Java framework for developing ops-friendly, high-performance, RESTful web services.

It's a nice microframework which comes with built in health-checks, and metrics and it's also ops friendly because it deploys as a single JAR file.
> When I think about drains on my time and productivity, I've never been too setback by having to deal with a "for" loop instead of something more monadic. However, I HAVE spent days doing painful refactoring work, that could have been done in minutes with a few right-clicks in an IDE.

I think your examples betray your inexperience with what you're criticizing. A for loop isn't somehow corresponding to "something monadic" and safe refactoring (actual refactoring, not just renaming things, though that's obviously trivial as well) is extremely easy to do and produces great results in languages like Haskell, OCaml, etc.. Primarily this is because moving grouped things is nowhere near as sensitive as in a language like Java or the like.

But yeah, you can right-click rename all day, for sure... Never mind that other languages can let you safely re-architect the very bones of the solution with almost zero fear of coming out on the other side in failure.

Java has great tools, but let's not bring up refactoring as a real strength. It's kid's level stuff in comparison to languages that allow you to do that and more without tooling.

Haskell et al. have crap tooling and that has real consequences, but refactoring isn't one of the casualties at all. They're still better at refactoring, re-architecting and repurposing than any of the big name languages.

At least bring up debugging, system interaction or something.
No php composer either.

Keep in mind it's in beta.
Conceptually, it's similar, and after git rebase --autosquash, the result is the same. But you can amend/fixup (call it whatever you want) any commit in your branch, not just the last one.
No offense but on the pre payment thing you sound like someone who was fortunate enough to have a vast network of clients you already knew and trust. Which is not the case for most.
I would consider price matching something before or during the same time with your own phone. As you have no idea of what algorithm is being used to show the price he is getting on his phone for the same item. Your's may be higher or lower than theirs.
Silicon Valley-Backed Venture Cleared to Become 14th U.S. Stock Exchange
Agree. You can't rely on everyone's behaving rationally. You should rather expect panic.

Though knowing there could be smoke or you might need to crawl will trigger thoughts at least in a subset of people and will increase an overall survival rate.

As for life vests - even in Hudson accident they were left unused. Maybe in the 1960s they were helpful but for now they look obsolete. Chances are you'll get fire rather than ditching. I feel their value is more psychological.
Within the office...most people know/can guess each other's fairly accurately.

I stopped talking to family about it though. Different countries and CoL means my raises end up being more than their total package. So discussing that leads to nothing wholesome. Instead I try to silently absorb more of the family costs than proportionate.
If you owned enough assets that could be used as a collateral, yes, you could request $1 salary. Many CEOs, Steve Jobs in particular, used to do that. He already had enough cash for day-to-day expenses (like buying a new Mercedes every 6 months); more significant expenses were financed... differently.

You should be already rich and structure your capital properly for this to work.
> Public transport is barely used.

In one of Uber's largest markets, NYC, public transport is extensively used, and I assume that many price-sensitive Uber users will go back to taking the subway or bus if Uber raises its fares too much.
It's not as easy a question as it sounds. Sharing this information within a company usually means trouble. So it doesn't look like a good idea to share it with society at large. At the same time, honesty and transparency is the best policy... Privacy, security, and psychological issues are at stake when it comes to money.

> the gig economy has made salary comparing a near necessity for many.

Obviously, most freelancers would love if this information was public.
If rates are public, you know where you are standing and where to start if you want to provide a service. That is not exactly the same as telling how much money one makes—one can only infer so much. Despite this, most freelancers are still secretive about their rate—as if this was always an advantage.
Python is left out too. It's a beta release so maybe they are not done yet.
This solves the problem of managing private artifact repos in corp-land. If your org pays for GitHub, now you don't have to manage them. The only thing they need now is their own CI, and maybe some improved project management, and GitHub's going to be one gigantic gravy train.
By "lurking" people mean that the executives who care nothing about open source are firmly in control, and some day may try to assert their control in ways that nobody else likes.

You may not remember incidents like why Jenkins was forked from Hudson, but Oracle is run by people driven by what they think they can get away with, and not by what is good for the projects that they have power over.
Yes, I suppose this is also correct. I just wanted to reiterate that with modern creative financing, a large company can stay “unprofitable” basically forever and still keep shareholders happy.
>forces me to use a different browser on my phone versus my desktop

Firefox has a desktop version too. Works well.
I'm using it to differentiate between summarizing (removing steps between A and B) and modifying (introducing new steps, reordering them, or editing them).

You can do it in a way that isn't harmful (as I mentioned earlier), but good luck getting a team to actually stick to that. It also doesn't help that pretty much no tooling encourages doing it properly.
I haven't used Firefox on Android in 6 months or so but it was pretty stable for me.

I switched to Brave for mobile and it is amazing. Super easy to block scripts and other tracking without hijacking your DNS or requiring ad blockers/pi-holes etc.
GitHub Actions?
Also to your point on how mutation happens: its random and rarely beneficial. If you go out in the sun without sunscreen, that UV light penetrates your skin and encourages your skin cells to produce more melanin, but it could also damage your DNA, break a tumor suppressing gene, and give you skin cancer.

Your bodies DNA replication machinery also has an error rate which can be worked out, and you can extrapolate that to get a rate of mutation. Knowing this rate can give you an estimate of how long ago two species diverged based on the number of different bases when you line up their DNA sequences against eachother, for example.
Poor start-up time, terrible application bloat, uninspiring language with poor concurrency support, massive RAM requirements, everything XML, complex tuning required, what a nightmare.

No wonder the world is running towards Python and serverless as fast as they can...
What are the downsides of this?
debian packages are also supported it seems: https://github.com/git-lfs/git-lfs/packages/5789 and https://github.com/alteregofun/firsty/packages/2953

found a ruby one: https://github.com/wintron/hola/packages/4057 (yes! got it working)
Have you tried Bintray? [1]

It's made by JFrog (makers of Artifactory), it's been around for while, it supports lots of formats including harder ones like apt, and it makes package distribution about as easy as it can be.

[1] https://bintray.com/
Employees at a workplace knowing each others' salaries puts them in a better position in bargaining with management but it also makes it harder for management to selectively give certain employees higher salaries - because the employees are talented or because the management happens to want to keep said (maybe talented) employees or because management just like certain employees or because management just wants bargain each employee down to minimum management thinks they'll take.

So the question is what situation would someone think better serves their interests? Of course, whether one person describing their salary would evoke reciprocity or not is a question, whether another person would tell the truth is a question.
That's an interesting definition of "made"... assumes the concept of liquidity has no meaning.
> There aren't many definitions of freedom that include state control of your children.

There are some: freedom from violence in the family, freedom from mistreatment, child labor, indoctrination, ...

Essentially this is about balancing the freedoms of the parents to raise their children according to their rules against the freedoms of the children to receive a certain kind of education. I am quite happy this is something I do not have to do, as I fear it’s a very delicate decision to make. And I doubt anyone involved takes such a decision lightly.

> When you can't opt your children out of being indoctrinated, it's pretty clear that you're not free.

True, but then indoctrination of your children might be the least of your problems.
I'm not talking about squashing the feature branch. I'm talking about squashing all of master down to one commit (initial commit). If you don't take care of your history, my question is why do you keep it at all?
I don’t think is true anymore.

The .net 5 announcement was very clear that .net core is the future and its been a while since you’ve had needed things that are windows only to build a non-trivial .net core application.
We use dbup[0]. Its philosophy[1] is that you should treat your DB changes like code changes in source control, and only perform up migrations. I agree with this. We previously spent a lot of time and effort writing down migrations that were never, ever used. If you need a down migration, take a backup before running your up migrations.

We're a C# shop. Our DB migration scripts are simply named with a datestamp and a change description. The scripts are added to a console exe project as embedded resources and everything is committed to source control. These exe projects are very thin and contain a single line of C# code that passes the command line arguments directly into an in-house DB deployment library which is installed via nuget. This library handles command line parsing and executing dbup in various ways, using the scripts embedded in the calling assembly.

The result is a simple executable file that, depending on its command line, can upgrade the DB directly, preview which scripts would run against a particular DB instance, test the DB deployment against a clean SQL Server LocalDB instance, or generate SQL scripts for DBAs.

One nice feature is that the exe can also return the connection string of the SQL Server LocalDB test instance to external code as a test fixture. We can use this to directly unit test our repository types against a real, clean database. When the test fixture is disposed by XUnit, the temporary DB is cleaned up and removed.

The console projects are built and tested as part of our CI builds, then pushed to Octopus Deploy[2] as packages. The Octopus deployment process simply runs the executable and passes it the connection string of the DB to update.

[0] https://dbup.github.io/

[1] https://dbup.readthedocs.io/en/latest/philosophy-behind-dbup...

[2] https://octopus.com/
But to that point there was no "IPO price", i.e. the price paid by institutional clients before the first day of public trading, so there was nothing to fall below (there was a "reference price", but that's just more like the MSRP given by the stock exchange, not what anyone actually paid).