skysight-inc/HackerNews huggingface dataset:
Not only that but it also feels like everything is floating left. (Which it is but when there's nothing on the right scrolling down it looks out of place.)
I'm pretty sure I read somewhere that at least 50% of the vms running in Azure are actually running linux.

And in this case, "action" refers to the ci/cd tooling github provides called "github actions". It's one of the tabs at the top.
Conventional type systems don't really help you when your code is pretty much just taking in vectors/matrices of floats and returning vectors/matrices of floats.
This should be to most up-voted comment.
There is a setting or an extension I use to mute all sites by default. You can then whitelist domains one by one. It’s a lifesaver.
CCPA applies to CA orgs with a massive bottom line. HN assuredly doesn’t fall within CCPA’s crosshairs.
> I think that was and is China’s goal

I agree, and with the recent outbreak, I don't think it's possible, at least not for China. New Zealand has a shot at it.
Does this not apply to Paypal? Because I read some ridiculous requirements on coin sites, such as sending scans of your national IDs or even doing videos of yourself.

All the while Paypal only has name and address and perhaps a credit card number.

Seems to me coin sites are either smothered in red tape or so afraid they go above and beyond the legal requirements.
Weill, this only "works" for you if you trust google. Given multiple security incidents in the past I am certainly not one of those people.
I answered you in two replies already, but you will have to define "polite conversation" for this one to make sense. Anyone on the left who calls for or hints at purges in the same way that white nationalists do doesn't even make it onto the national stage. If you define "cancelled" as "losing their job and getting persecuted" then how about Colin Kapernick, for protesting police brutality by kneeling, and the worker who was (most likely illegally) fire by Amazon for pushing for unionisation amidst COVID19?

And being up Bernie Sanders name in "polite" democratic circles, let's see how supportive they are.

Reality is, the far left doesn't get cancelled as much because their popular ideas generally involve democratic control over the means of production and treating everyone like a human being, not revolution, while the far rights "popular" ideas are racism, sexism and the disenfranchisement of the "proles". One of these inherently requires authoritarianism, the other doesn't.
I do. In the age of various resolutions and screen sizes and css frameworks, websites can and should be designed to look reasonable on any number of horizontal logical pixels. If it isn't supposed to be wider than 1400px, that's what css's `max-width` is for.
Plenty of selfish/oblivious drivers, but don't overlook the selfish pedestrians causing intersection traffic backup too. There are plenty that are crossing right up until the light is red (even if they don't have a "walk" signal), making it impossible for more than one car to make the left turn. Everyone needs to work together.
You are correct, however that's a niche use case that would warrant using a non-conventional type system. Conventional type systems are mostly for just dumping a bunch of strings and integers to and from a database and formatting them neatly.
If you remove monadic IO, laziness and immutability from Haskell, then you're a lot closer to OCaml than you are to Haskell.

But more importantly, immutability is used everywhere in the industry.
Yes, you can look at the code here: https://repo.or.cz/tinycc.git/tree
Could have done without the music in a coffee shop right now. :)

I normally always have my laptop on mute, because I'm paranoid about bothering people.
Yes that is true for Excel but that is not true for Github.
That's the dangerous way of thinking. As far as I'm concerned and seen projects fail because their either build the wrong thing, or don't deliver (on time).
The practices can slow you down, but they can also speed you up.

Sometimes the failure to deliver is a managerial failure or the problem is too complex for the team tasked with it to deal on deadline. It's rarely because of "we keep code clean and production running" or "instrument everything".

What I've seen instead much more often is that good practice is replaced with common practice or deviation (problem) is normalized.

The latter leads to some rather interesting failures - bugs, and failing to deliver. Sometimes explosions if you're dealing with rockets.

I've also seen bad workflows cause serious slowdowns and issues, while not being replaced because things are "done" on paper. I find this on par with lying to your boss, which it is. Also in case of bigger multiple teams, tardiness to implement improvements because someone might have to change something about their setup, instead of engaging them with a discussion, leaving it for a flag day. (When everything invariably goes wrong.)
That probably helps, though many of my issues have been other problems, like xorg, the nvidia driver, grub (or now systemd-boot)
I think it got misunderstood
> Porting from PPC to x86 was arguably more difficult as a lot more of the framework code had endianness assumptions baked in.

Did it? The code they inherited from NeXT didn't assume endianness, and until Rhapsody Developer Release 2 they shipped x86 builds. Some applications like iTunes ran on Windows, with a partial port of the Cocoa libraries underlying them (this, too, was a descendent of old NeXT support for Windows).

It's entirely plausible that Apple didn't have to do much; as they said at the time, they never stopped supporting x86 after Rhapsody Developer Release 2, and they had the OS running on x86 the entire time. I'd assume from the point of view of most developers working on OS X they simply had requirements to avoid endian assumptions, etc., and occasionally the team maintaining x86 support would send a nondescript patch to "fix the endianness assumption".
I'm not sure if you're being facetious or asking a genuine question. The answer is "yes", with the exception of the word "actually". The "eager subset" was written to target a pre-existing runtime, which before then only supported an in-house, fairly poorly-designed, functional language called Lambda. Some of the team there wanted to be able to use Haskell instead (understandably).

For stuff that doesn't require that runtime (as convenient as it is) they just use familiar old lazy GHC. My understanding is that they are progressively moving more and more to GHC, although my knowledge is five years out of date.
Post from the same author on Google: https://insights.som.yale.edu/insights/the-antitrust-case-ag...
My opinion is that Github now looks like a default bootstrap theme.
For someone who wanted to read more about Fabrice Bellard.

https://web.archive.org/web/20110726063943/http://www.freear...
Nonsense that Apple would buy DuckDuckGo. DGG is just a wrapper around Bing Search. Therefore Apple could recreate DGG from scratch in a month.
There's no obligation to be civil to people who are being uncivil.
What I have realized over past few years, organising code for future is a function of a characteristic of an engineer.

I have noticed people who are extra organized in real life, who keeps every single file in a right directories after download tend to have inclination for prematured code refactoring for future use.

If these guys become code architect then i end up doing so many unnecessary things. The fundamental assumption of the refactoring gets changed very fast and the code needs to be rewritten for the majority of the cases.

From a company level I find the instructions are clear, mostly holding the same contract between services as long as possible and less schema change.

Its the engineer with subjective idea of perfect code / supporting future work makes it even more complex
Even if the baby has trouble getting the thumb into the mouth at first, it has no trouble sucking it. Or any of thousands of other instinctive behaviors.
I guess you have never seen a Stromer[1]. The iPhone of e-bikes.

[1] https://www.stromerbike.com/
Playing music is a terrible idea.
I wrote about this a few years ago.[0] The gist to avoiding premature over-architecting is to keep sticking with as static/hardcoded behavior as possible to meet the requirements. Just make sure it’s well organized and cleanly written in your language of choice. Then over time add configurability to that behavior as specs change. Architecture is easy to change not when it correctly predicts future change (almost impossible), but when it is straightforward enough to follow and reshape.

In my experience, keeping behavior static/hardcoded is the architectural equivalent of avoiding premature optimization.

[0]: https://max.engineer/cms-trap
We have one! I thought it was super overpriced, but my wife uses it every single day for hauling kids around.
Sarcasm is nearly impossible to detect in writing.

A tip: If it seems the whole world is a problem, it's probably not the world that is the problem.
I think this feels disappointing because you’re saying that my anecdotal evidence — that the matrix ecology of proper nouns is confusing to newcomers — doesn’t bear true in the wider world. That feels surprising to me.

If I could wave a magic wand, formatting matrix usernames as “alice@alice.com” instead of “@alice:alice.com” feels like a similar opportunity to make things more friendly to newcomers.

It’s these little things that make a huge difference to success. TL=com/ORG=ycombinator/HOST=news addressing vs news.ycombinator.com. Or calling Outlook an “MUA” instead of just saying it’s a “mail client”.

It’s technically correct. Some people say that technically correct is the best kind of correct, but often it feels like the most convincing strategy is the one where you don’t need to add explanation or bon mots to win over opinion — people can just see it’s right.

I’m surprised that Matrix didn’t think they would benefit from trying to become well known as Matrix first, then diversify into FluffyChat etc second.
Yeah, the organization of data (and the data itself) is really the only thing that matters. Code itself is cheap and disposable. Just write the minimum number of lines of code required to get the job done, but spend time on the data model. And because you're not anticipating any future use cases, your code is often so short it can just be thrown away in the future.

A larger codebase than solves the same problem as a shorter codebase is almost always worse, has more bugs, and is harder to maintain. Code is the enemy: the only good line of code is the line that doesn't exist.
Between uBlock Origin and uMatrix I hadn't even realized. Prior to seeing these comments I had actually been impressed by the site's (apparent) responsiveness combined with the (apparently) clean and mostly pain text layout. Whoops.
> This won't end well (imo).

People have been saying that for decades. How many decades of successful operation are worth then having a couple of years of "won't end well"? Also why do we think that any other system would "end well" (whatever that specifically means)? It's not like there were never any economic crises or instability before FED and other organizations started manipulating the system that way.
Would this also make p2p tech illegal?
It's called an electric chariot, thank you.
Server logs can't do this job well.

If the system is designed well, in a lot of cases the users won't be receiving the resource from your server, they will be receiving it from a) their browser cache, b) their local network cache, c) their ISP's cache, or d) a CDN. Your server logs might be showing several thousand hits while the number of times a page is actually shown to somebody might be tens of thousands of hits.

Server logs are great for logging what is happening on your server, but awful for understanding your user base.
Check out Jean Rondeau’s version recorded on the harpsichord. It’s honestly beautiful and the Goldberg Variations is one of my favourite pieces of music. It’s on YouTube :)
A good read for beginners. I believe the literature about ML state seems to be a little dated with current times. People and companies are at the phase of already implementing ML in their companies, versus figuring out things: How? The ML field gives you options for every user and different levels of expertise. Advanced user: TF or Pytorch, preprocessing: Beam or Spark. Accelerators: GPUs. Tools such as Bigquery ML and AutoML have helped users to get into ML by generating MVP in an easy way. In would love to hear more from people in the field.
Out of curiosity, how and how often do you make use of Haskell's laziness, and how often does it get in your way?

And yes, the syntax of Haskell (besides unary minus) really does feel like it's close to some kind of optimum.
Ehh, that reads like shoehorning in a political agenda to me. The hyenas aren't dangerous because they're foreign, they're foreign because they're dangerous. Their actions make them a threat - they're sneaky, mean and evil. That's why the lions don't accept them.

Timone is also foreign.

But like, if you want a parable they already gave you one: they aren't immigrants, they're Nazis.
Fascinating read, although I take issue with its title that implies that it's a bug in the chip. Maybe a bug in the author's code (when he wrote wrong values to the register), definitely not a bug in the chip but a feature. If you write undocumented values into a register, undocumented stuff happens. A lot of ICs have undocumented test modes that are used by the manufacturer.
Root some android, install obscure build, install firewall, use exotic browser.
Oh dear god, people took my post seriously? I meant it as overwrought sarcasm. No wonder I got so few downvoters.
I think the music was the punchline.
(1) bikes are priced disproportionally high compared to cars, (2) e-bike even more so, (3) this is a top of the line model from a fancy brand, (4) cost of ownership of a bike is a very small fraction of a car, with a bike when you've paid for it you're done, maintenance is cheap and DIY. Cars: insurance, expensive maintenance, road tax, fuel etc.

Personally I almost always buy my bikes second hand, there are always deals to be had where bikes are only a few months old and are sold with a 50% or more discount.
Just click the X in the upper right corner.
After 6 months of practice only few bikes were faster than my scooter (25 km/h), I never experienced issues with turns.

Only issue is the rough roads - when I want to ride on the rough roads I use bike.

In every other aspect e-scooter is better: doesn't require special outfit; I don't sweat; it's compact enough to take it to the shop or cafe (without bending); less details I need to care about - pedals, brakes, speed switches, saddle - I just use what I've bought and it works fine. My bikes usually worth ~$500 (same as e-scooter) and they requiere some fixes/replacements from time to time. Scooter had just one flat tire replacement, that's all.
Awesome. Thanks for the explanation.
The 3700X CCX die has 8-core+36MB L2+L3 cache and is just 74mm2, the IO die has pcie4, ddr4, other IO and is 12nm 125mm2. For a total of 199mm2.

If you want to compare cpu, graphics, video and nn, then the AMD 4800U die size is 156mm2, this chip has +4MB L2+L3 cache (12MB total), a much better GPU+FP16 for 4TFlop nn, and full AVX2+SMT cores more than the A12Z. The little A12 cores might be full ISA, but they're 1/3 the die area and are lower performance. NEON is half the size of AVX2 and the GPU difference alone would likely push the A12Z past 156mm2. And there are 15W/45W versions of this chip going as low as 10W. The A12Z is likely around 10W+ too in the iPad Pro and the devkit, but I can't find sources on this.

Looking a lot more competitive now isn't it?

The Qualcomm 855 is 73mm2, and the A12 is 83mm2, and the performance gains here are impressive. Beyond this, A12Z 120mm2 vs AMD APU 156mm2 and it's starting to look like a much closer fight, and by no means a perf/watt or perf/$ advantage for Apple until we see real systems.

Die size is _the_ trade off Apple is making with their ARM/RISC+loads of L2 cache design. It's a trade off every chip makes, but it's especially important here with large cache sizes. I don't doubt in a couple of generations Apple can compete with an AMD 4800U CPU+GPU on real world multi-threaded tasks at 10W (assuming 15% increases/gen), but the 4800U is already a few months old now. Apple fanboys never learn. Sigh. Also, Apple fanboys are the new Intel fanboys when stressing single thread performance.

Sources:
http://www.hw-museum.cz/cpu/414/amd-ryzen-7-3700x
https://www.techpowerup.com/264801/amd-renoir-die-shot-pictu...
https://www.cpu-monkey.com/en/igpu-amd_radeon_8_graphics_ren...
https://en.wikichip.org/wiki/qualcomm/snapdragon_800/855
https://en.wikipedia.org/wiki/Apple_A12
>Do we really need another chat app? Wouldn't it maybe be >better to capitalize on the existence of an open network >that is already around, and build a better client for it >that kicks the pants off of whatever's already out there?

First thanks for the reply
I could have explained this a bit better it isn't a chat app replacement, not trying to dislodge messenger, whatapp, etc. Group and direct messaging is core to the product but not the value prop just by itself.

I am specifically asking the group chat part as it has been done meany times so I would like to not make it again but use already built or at least mostly built. Then can focus on other part that makes is unique and makes it valuable.

>Then who's going to build it? Are you hiring a team to do this? Don't underestimate >what's involved here to get something working and keep it running. At the very >least, if you don't go with a decentralized model, you're in for expensive server >bills and considerable ongoing maintenance to keep up with security patches, etc.

At the moment I have someone part time who is smart but is still learning. I may also hire a very small team but thats the reason I am trying to get a full understanding of options and pros and cons, so there is a clear roadmap.

>There are already too many options in this space. Why would anyone choose your >client when Signal, Telegram, Riot/Matrix, etc. are all free and decent to use? >What is your unique value-add?

By too many options I mean frameworks, languages, backends, etc. That why am soliciting feedback from HN on it.
Again it isn't a signal or telegram replacement. Group chat is core to the product but not the value-add. It isn't a slack replacement, no web or desktop. Just iOS & Android. The nature of the product it does have to be on both, can't start with only one.

>Don't do this unless you have a business plan good enough that someone will lend you >$1MM to get it off the ground. Seriously. You're talking about entering a massively >crowded marketplace, and you're clearly out of your element.

I have already brought my tent to Sand Hill road and written out my cardboard sign. (j/k)
But again not replacement for existing options. I have lead the creations of products before. I asking newbie questions because I want to see the situation with no preconceived ideas for this specific part.
The value in DDG is the userbase and brand.
That’s the punchline.
They look interesting but are illegal in the UK.
Twilio’s Dutch rival MessageBird plans an IPO
That would be leaving a lot of money on the table up for grabs by your competitors that do know how to see through this situation.
A useful wrapper for starlette – starlette-skin
starlette-skin make the superfast python starlette framework more easier to organize code, and add postgresql and redis easy-use interface in it.
Bigger wheels.
"A country is not made of land; a country is made of its people" --Unknown https://archive.vn/bS2fL
I don't mean it's literally bad for your eyes - there may well be benefits to constantly shifting your gaze/focus/etc. I can't comment on that.

I'm talking about "natural" eye movement being a well-known design principle. This means that eyes very naturally follow a Z pattern that doesn't exceed the periphery of your focus. So if you load up a fresh page, your eyes will naturally look top left -> top right -> bottom left -> bottom right, bounded by your standard viewbox (which is about 800px-1200px wide at 96dpi and 1-2ft, the standard distance most people sit from their monitor). So you usually stick your most important information along that pattern. Anything outside this boundary requires an extra "look", which means a slight hesitation/delay on the part of the user. That's not to say the space is unusable, just that you put your most common/important features/information along this flow.

It's also not an ironclad rule, but it does work very well. When I went to the old GitHub, my eyes always followed the same pattern: repository name (top-left, to make sure I was on the right page), account (verifying that I'm logged in), branch, clone/download, then file list or more commonly, the README (bottom-left). It was a very quick, natural way to navigate a random GitHub page.

Now, I literally have to move my head to do this. The weighting also feels completely unbalanced, like there's too much information on the left it's all slanting in one direction.
>way before even talking about compensation.

Is not this the problem? The vast majority of vacancies I see as well as recruiters offers do not have salary. So I just ignore them. This is also why FAANG has no problem getting candidates and can haze them to their heart's content. Even though they do not list salary too, people have high expectations and apply in huge numbers.
Happens with bikes as well. People wear helmets for a reason.
Yeah, I wish somebody invented a sarcasm punctuation mark /s
I’ve been using this setup some Christmas and also find it works incredibly well.
I think Rosetta is mostly about userspace, and a Hypervisor is definitely not something that sticks to that - modern VMs run on the bare metal thanks to CPU acceleration and dedicated instructions (i.e. VT-x and AMD-V). Getting an app to run on a foreign architecture it's different than emulating a whole machine in order to get an unmodified OS kernel to run. You can do it this very day with QEMU, yesterday I tried just for fun to boot Windows XP on my Raspberry Pi 4 (it boots but it's horrendously slow, if you're interested). Maybe with time and effort, an emulator can get a satisfactory level of speed (probably never enough to run Windows games on emulated Windows though, but who knows).
Try 10+:

https://www.utrecht.nl/fileadmin/_processed_/1/b/csm_fietsen...

That garage holds 12500 bikes!
I don't think it's safe to assume that Pegasus can't manage persistence. This isn't run-of-the-mill malware we're talking about.
Notebooks for iPad
Show HN: Endorse – Share your favorite recommendations with friends
I'm having a hard time seeing PageRank '99 being ML just because it uses a lot of data and is linear algebra at the core. It's one large eigenvalue problem.
I don't see how having national backed social media platforms to the likes china does is a better alternative for end users compared to facebook.
If you are a proponent for open speech this will accomplish the opposite since it simplifies state issued censorship.

I understand that bashing on facebook is a popular narrative here and they have made significant mistakes but it can hardly be argued the platform doesn't bring value to a significant share of people.
Hacker News attracts a lot of smart readers, so I'm kind of surprised that your comment actually 'fooled' people. It was very obvious sarcasm.
Whilst TCC's bounds check was rare for quite some time, the bigger compilers do now actually offer it.

Clang supports bounds checking as part of -fsanitize=address, (though with a few more flags you can _just_ have bounds checking instead of the other sanitisation options). (Since around 2015?)

GCC supports bounds checking and others, depending on which frontend you're using the options can change. (Like -fbounds-checking for C, and -fcheck=all for gfortran). (Since around 2013? GCC 4.71)

Even Intel has -check=bounds. (Though not under macOS). (Since around 2015?)