skysight-inc/HackerNews huggingface dataset:
> Some groups, such as Fins Attached, Shark Savers, IUCN, Shark Angels, Shark Whisperer and the Sea Shepherd Conservation Society, discourage consumption of the [shark fin] soup due to concerns with the world's shark population and how sharks are inhumanely finned alive and returned to the ocean, unable to swim, hunt or survive. The prevalence of shark finning and the sustainability of shark species are both debated.

If they were actually killing machines, all we would need to do is stop holding back and sharks would go away.
Throwing money doesn't solve a problem when you don't have the right people.

Took them quite a few years to fix a keyboard on their macbook line for example...
This is overkill for 90% of projects out there.
Your theory makes sense if people buy only one phone in their life time.
Brainfuck has a language specification (it's nice and short) https://esolangs.org/wiki/Brainfuck and a long list of implementations, some even hardware backed. https://esolangs.org/wiki/Brainfuck_implementations

So if that's the criteria, then brainfuck is a serious language.
Run the DB in docker, import the stored procedures as part of the setup migrations and run tests against that from your normal test suite.
Despite trying and reading it carefully I didn't understand it. I wonder if it is me or the article, or both.
NSQTracer to watch published NSQ messages (Go)
Saudi's national AI strategy to be announced tomorrow (LinkedIn)
There is also a blog post on this: https://medium.com/palantir/a-pyspark-style-guide-for-real-w...
Actually, I don't think this is about trust. I mean, when I use an Apple OS, I (should) trust them, as their software has access to all my most sensitive digital information.

However, making it impossible to route the traffic of the system apps through a VPN of my choice (whatever the reason), is just broken functionality.
The "Vietnam" article referenced in the post makes some very valid points about ORMs and their marriage to Relational data.

When using Object Oriented Languages, like C# / Java / C++ etc., the programmer is forced to represent data into objects. True, representing table and relations between tables as objects is difficult, but do OO programmers have any choice at all?

Afterall, the issue is not a single table (a row can very well be represented in OO constructs), it's the relation between tables that causes headaches.

Even when using languages like Python, I have to inevitable gather related pieces of data together, in a dict say, and it still feels like mapping related tables to objects.

Another contention with the "vietnam" article is that the author assumes that OO programmers will want to use inheritance to model relations between tables. This seems outdated in my view. Composition is more suitable and powerful and is almost always used in ORMs, for ex Entity Framework.

The original post also claims that ORMs tend to gravitate towards "select *" queries. This is true, but has many solutions. Many ORMs optimize queries based on required columns. But there is also another issue with this. Say you have a table with 100 columns, but are only querying 5 at a time, isn't it prudent to separate out those 5 columns into another table? Or perhaps create a view? If the use case demands just 5 columns, but the table has 100, isn't there a problem with the data modeling rather than the ORM?
>Is warren buffet himself not an example of someone who has been able to consistently generate alpha?

Sure but the exception proves the rule. We don't have a whole generation of Warren Buffets, we only have one.
I much more common use case for people using camera gear, not smartphones:

most digital cameras don't have GPS tagging, but we carry our phones with us. some of us use google maps timeline, which records all our movements and we can download this as a CSV. for privacy concerns, one can use a gps recorder app instead. if we can match the timestamps of the kml / kmz / gpx file with the timestamp of the camera photos (and adjust timezone differences), then we can geotag digital camera photos that initially have no geotag information. the tools that are out there who do this are cumbersome and difficult to use.
FinTech Innovations Improve the Customer Experience
The Memo by Howard Marks
Antennas, batteries, back panels, circumference of front glass panel, metal frames for the panel, etc.
I am on Windows and I would like to use ungoogled Chromium but I don't see it as a choice because it does not have automatic updates and I am concerned about my security. I suppose this is a solved problem on Linux?
No idea. According to Google these phrases only appear in this blog post. A strange kind of common knowledge.
We've got various number types in array form: {u}int{8,16,32}, floats too.

I feel like that is about the best we can do without harming backwards compatibility. They are there when needed, but we are stuck with the ambiguous "number" type in general.
It makes a lot of sense actually. I think expiration dates on webpages is a great idea. People who care won't be surprised that way.
There's a big difference between HTTP, Apache, and ORMs. People not understanding why they're different is what sinks companies all the time.

Using any abstraction is a gamble that it doesn't leak before you have the resources to fix it.

HTTP is a terrible comparison because in almost every domain you will either make millions or (far more likely) fail for other reasons before you need to understand how TCP/IP works.

I bet there's loads of companies that have died a slow death, releasing everything a month later than they want to, because the back-end developers aren't comfortable with whatever the stack of the day is and they were too busy learning yesterday's stack of the day instead of the intricacies of the language they're working with, or the standard library.
<author deleted his comment because his doesn't have much to say>
Apple could stop allowing you to load kexts they don’t sign, like they do on iOS.
Demo Shows the Power of Photoshop’s New ‘Smart Portrait’ AI Filter
Geogoo.net
It is more like the blood collection solution your doctor uses also happens to collect a bit of DNA on the side and sells that to third-party buyers ('legit' or otherwise), and the doctor is either unaware or doesn't really care.

In which case your options as a consumer is either to say "my options are sucking up the humiliation and massive invasion of privacy and having the blood test, or not having it done at risk to my health" OR if you have the means to find the resources to attack either the blood company or your doctor where it hurts (i.e. financially), either via a lawsuit or a successful PR campaign etc.
ORMs are good if you already know SQL.

Not all ORMs are created equally.

I enjoy the Django ORM and it's composability, OTOH I was really not keen on earlier ORMs.
You're assuming the UK has a coherent policy that stems from brexit. I would dearly love that this is part of a grand unified 25 year plan (or in fact any plan that isn't "get boris to PM and keep him there")
Indeed - integrity should be dependent on the content, not the URI. It looks like they do it to allow "replacements" (e.g. serve package version x.y.z-1 if it can't find x.y.z).

This sounds like a horrible idea.
It's certainly a valid observation that anything that large enterprise does, will end up being more complex than it necessarily needs to be.

But if I look at a lot of the SP anti-patterns I've seen over the years, some common themes start to arise. I'd say the biggest issue is that it is more complex to maintain interfaces between two discrete systems than it is to write monolithic code paths. Seeing SP_ProcedureName accompanied by SP_ProcedureName_New is very common. It's easy to get into that situation, and tedious to get out of it.

Storing business logic in the DB also presents a lot of very tempting, but ultimately costly, shortcuts to developers. Using a non-temporary table when you should have used a temporary table, because you wanted debugging to be easier, but now you've got a concurrency issue, but it'll probably be OK, so you leave it there for 15 years. I have also never seen what I would consider to be a sensible use of a trigger. You also end up with SPs invoking SPs invoking SPs... and figuring out the side effects of calling something becomes a lot more complicated than it would be in a monolith.

I don't think they're always bad, but I do think that reasonable use cases for them are rather uncommon. When you had a lot of services directly consuming one database, SP interfaces used to make a lot more sense. But that's not a very common architecture is not very common any more. Even in large enterprises, you'll typically see new projects being developed as web applications, even if they're only served over the corporate network.
This declarative narrative is more or less a marketing gag, isn't it? Mixing Logic and Markup has always been an antipattern in web development. However, react calls this declarative and this is the new black now?
Apple Security Updates
Find this very scary not having RCD on some plugs even with 120 Volts. Sure 240v with RCD will give you a massive shock but still will very unlikely kill you. No RCD on the other hand can be fatal on 120V:
https://edition.cnn.com/2017/07/18/health/teen-bathtub-elect...
> If you have a monolith, now you’ve got a distributed system.

You already did, you just chose to ignore that the DB is actually a separate service. Ignoring this has meant that I've spent a not-insignificant amount of time in my last few jobs cleaning up bad ORM code because the queries performed terribly. I've cleaned such messes as pulling in all rows and then looping/filtering on them client-side, just generally querying for too many things/too many columns, querying for data and then looping over it to do more queries (instead of figuring out how to do it in a join), etc. When people treat the database as if its part of your monolith, because all the query logic is locally part of your codebase in your ORM, there's a temptation to be lazy and treat it that way. And it works fine in development because the database is small with only test data, but can be painfully slow in production.

I'm sure plenty of people do it properly, even with an ORM, but I've had to clean up the mess too many times now, across multiple companies and dev teams.

I'm not advocating for putting all of this logic into stored procedures, I think that's going too far in the other direction, only that you already have a distributes system, if you have a database, where the boundaries do matter.
Replit Classroom Data Export Guide
Allow me to recommend another current HN front page article in response to this: “Discipline Doesn’t Scale”, https://www.sicpers.info/2020/10/discipline-doesnt-scale/
You might have 208V and not 240V if you have two 120V phases 120 degree apart.
>[...] discovered that access to object properties is faster than accessing array indexes half the time. That was in C language, but it holds true in JavaScript.

What are these object properties in C?
From Co-Ops to Cryptonetworks
Isn't this the same as function overloading in some programming languages?
Even for shell scripts? I'm still on Mojave, and now I've got even less appetite to upgrade.
Life and Investment Goals Intersect
Gold Signals

Gold Signals

Forex Signals

https://www.gold-pattern.com/en

Set up an investment goals workflow

Investment objectives address three main areas related to money and money management. First, it intersects with a life plan that engages our thought processes in unexpected ways. Second, it engenders accountability, forcing us to review progress on a periodic basis, invoking discipline when needed to stay on track. Third, the drive that affects our non-financial selves is created in positive ways that can improve our outlook on mental health.

https://www.gold-pattern.com/en

توصيات العملات

توصيات الذهب

The Australian Investors Association recommends using the SMART format when setting investment goals. These are the elements:

Gold Signals

Specific - Make each goal clear and specific

Measurable - Frame each goal so you know when to achieve them

Attainable - You need to take practical action to achieve a goal

Gold Signals
Your typical micro-service architecture will run into a lot of the same types of problems. The cost of maintaining those inter-service dependencies easily gets quite high, so if you're going to commit to that, you really should first understand whether you're going to be deriving any benefit from it.
You're welcome. For some other really nice saxophone: Anything by Steps Ahead, Grover Washington's record 'mister magic'. If you want more drop me a line by email, I'll do some digging in my collection.

To give an idea of the range of saxophones:

https://en.wikipedia.org/wiki/Sopranino_saxophone

https://www.youtube.com/watch?v=7XqwC1NmtG4

to

https://en.wikipedia.org/wiki/Subcontrabass_saxophone

https://www.youtube.com/watch?v=kgt2m9Q7Kz0
We have to support both MySQL and MSSQL so Hibernate has been mostly great for that. For really simple queries it's also nice to be able to write "findAllBySomethings_IdAndPropertyIsNull" etc instead of writing a SQL query. Been there, done that.

Though I have to admit I do check what queries Hibernate produces to make sure it's not doing some funky stuff that's not really needed (as a result of a mistake of my own, mostly)

Edit: It has come to my attention that it is ofcourse Spring Data that offers those named queries. Still see nothing wrong with hibernate since I still only have to write it once and I'll be relatively safe supporting both db systems.
They aren’t exactly the same thing, but in this case there’s a replacement being done to get essentially the same thing as a “fix” so they’re evidently close enough for this case.
> Isn't that sort of like complaining that you can't use an Bing unless you "switch to an custom [search engine]"?

No.

> Does Google do anything to block you from switching to a different launcher?

Yes.

What you are effectively claiming is that integrating solutions to dominant products which do not otherwise need to be integrated for the product to function, is fine and does not constitute abuse of monopoly, because there are (non-straightforward) ways to work around those.

Which did not work too well for microsoft windows and internet explorer mandatory integration back in the day, and there's no reason it should work well with Google-branded phones and google search today.
There are two possibilities in C++. I am not sure what the situation is in Java.

It is possible to define a pointer to an object whose contents may not be changed. This is done with ‘const * type object’.

If you want a pointer whose value must not change, but do not care about the contents of the pointed to object, you would write ‘type * const object’.
Well we have a consensus system that's quite advanced to avoid poisoning and false positives. To put it short, all members have a Trust rank, only TR1 can publish an IP without counter verification, and only if it doesn't shoot a Canari from our whitelist of IPs. TR1 mean perfect accurate reports for 1+ year. All other TR level can partake but need counter verification from either our own honeypot network or other TR1 peers before being integrated. There is also an AI that will be trained soon to confirm false negatives and extract more complexe patterns.
Missed opportunity for the Maize Maze joke.
LSE-Traded Mode Adopts Bitcoin as Reserve Asset
in my anecdotal experience this almost never happens because devs have an aversion to putting SQL in the code.
Wow that dark blue step change is really impressive, very cool.

edit: I wonder if you could establish a correlation between countries that went into lockdown but still had high levels of basal seismic activity and total number of corona infection cases? As in people not respecting lockdown guidelines or countries implementing partial/selective lockdown having higher infection rates.
Given the simplicity of the RPi system, it's quite possible that the PCIe bus is clocked from the same source that you are raising the frequency of to overclock the CPU.

Since we saw a ~15% increase in NVME performance with a ~33% increase in CPU clock, I'd even go so far as to say that the 100MHz clock to the PCIe bus is somehow derived from the base clock in a way that means that any n% increase in CPU clock would yield an n/2% increase in PCIe performance.

This tracks with USB not seeing an increase in speed as that's likely clock stabilized separately.
Aren't things like Nuget supposed to solve this : https://devblogs.microsoft.com/cppblog/nuget-for-c/
https://en.wikipedia.org/wiki/Gradual_typing

Also, TBH, types are kind of the wrong answer to the question. The question should be: How do we make the language efficiently expressive? For my money, that means defining constraints primarily on the code’s main interfaces, which a given constraint may be a combination of traditional generics, dependent types, and/or declarative run-time checks on input/output values. (e.g. Eiffel comes to mind.)

For instance, in my kiwi language I can define an argument as:

list (whole number (0, 100), 4, 4)

Which is to say a 4-item list, where each item is an integer between 0 and 100. And since I don’t want to type all that every time I can give that constraint a descriptive name:

define type (CMYK color, list (whole number (0, 100), 4, 4))

I can even include user documentation in that definition so the whole lot’s self-describing.

Kiwi’s very late-bound and interpreted, so its constraints are implemented solely as run-time coercions with optional bounds checks; nothing fancy. But the semantics are quite well formalized so a linter could be implemented as an assistant authoring tool for users, and if you can implement a linter then you can implement a type checker; and so on.

What matters is that the language has a formal mechanism by which it can guarantee that a given value will always satisfy one or more user-defined requirements; and whether those requirements are checked at compilation, execution, or some combination is secondary to that. How rigorous the user makes these declarations, and if/where she makes them, is entirely up to her.

Remember, the goal of any language is to please its users. Not the machines it runs on, nor the designers who created it. And users’ needs are not constant, not even across the development cycle of a single program, so a language that cannot adapt to those users’ changing requirements as it goes has already failed its first hurdle.

..

Perhaps if authors of existing languages like Python and C put less effort into chasing the constantly-diminishing returns of post-hoc micro-optimizations, and more into thinking how to design the next generation of languages so as to carry forward the good characteristics of their predecessors minus their original already-painted-themselves-into-a-corner limitations, we might actually have languages that tick all the boxes by now.
I wonder if this has more to do with "Black Start" planning than actually providing power cross grids.

https://en.wikipedia.org/wiki/Black_start
Yeah at some point I should write a blog post, but here is a pretty good condensed summary of it:

https://old.reddit.com/r/ProgrammingLanguages/comments/jb5i5...

The mycpp tool I wrote can be thought of as a cross between this old "Shed Skin" project, and mypyc:

https://www.oilshell.org/cross-ref.html#mycpp

I kept extensive notes on the process on Zulip, list of threads ehre:

http://www.oilshell.org/blog/2020/03/recap.html#mycpp-the-go...

Really short summary: I used the MyPy front end, and basically printed its AST as C++. This involves a bunch of hacks, but it works.

The following conditions helped a lot:

- I control all the code in Oil, so I can statically type all of it, which involves both annotations and occasional patches. A shell doesn't have many Python library dependencies; i.e. it doesn't depend on BeautifulSoup or something like that. It's basically all string and data structure manipulation, with a few sys calls.

- Oil has extensive tests. I run the same tests against the translated and compiled C++, which flushes out bugs in the translator. (Something like 915 out of 1700 tests pass now, so the translation process isn't done.)

- I also used unit tests to generate some of the type annotations with pyannotate.

There is still some translation left to do if anyone is interested in helping. You will probably learn something about both Python and C++!
As someone with an inherited ocular disease, I'd like to know what diet and lifestyle changes you think I could make that could restore my cone function.
Yes, I remember when he did that with Christianity. I'm agnostic and I have his old books in my bookcase. He wasn't "criticizing" Islam, he was fearmongering. Then he started cozying up with evangelists as long as they hated "post-modernists" enough. He has (previously) had a lot of good things to say, and at some point he abandoned his ideals in favor of politics, and just became another Jordan Peterson crank.
> California had more rolling blackouts
> Let's consolidate it with the other grids

How about no? Centralization means single point of failure. If anything we need more, smaller, localized grids that are reactive to their localized needs.
The fact that a developer can "corrupt" the database with non-atomic stuff is an hint to me that the database probably doesn't have the right referential integrity constraints in place and probably is not normalized either. The relational model is built out of the box to keep a consistent state of the data and this is one of its main value propositions.

This is true when interpreted the right way, but I don't think real world problems are always so tidy.

Let's consider Standard Toy Example #17: The Bank Account Transfer. In a simplistic model, we might have a table of bank accounts in our database, and a second table of deposits. Constraints will guarantee that we can't do things like creating a deposit for an account that doesn't exist, but they won't ensure that if we create a deposit of X in one account, we must also create a corresponding deposit of -X for some other account so we aren't inventing or destroying money.

Of course, in a more realistic implementation, you'd never represent transfers between accounts as two separate stages like that, and if there is any single place to look up deposits into specific accounts it's probably some sort of view or cache rather than the authoritative data. But rather like going from single-entry to double-entry bookkeeping, to avoid relying on something higher up our system to ensure consistency, we've had to restructure our whole data model and the schema implementing it. In a sense, this is still just normalising the data, but that's a bit like saying implementing a word processor is, in a sense, just refactoring and extending a text editor.