skysight-inc/HackerNews huggingface dataset:
> all different ways to write `if err != nil`

Not hardly. This comment makes me think you don't have any significant experience with Rust.

> you don't even understand the challenges large code bases face

I've worked in more large code bases than I care to think about, including ones written in Go. In fact, one of the primary reasons I like Rust is because it gives me so much confidence when working in large codes. The compiler is ruthless! Data races won't compile. Forgot to handle a return value? Won't compile. Undefined behavior? Not likely. Async code that looks like sync code? You bet! I'm not hating on Go here; I think it's a fine language. And Rust isn't without its problems.

>continue with baseless zealotry

It's certainly not baseless, but I can see how it would come across as zealotry. I'm simply excited about Rust because it has made my life as a programmer much better.
There's a basic human need to be valued by others and to be part of a community, and the system we have now grades people according to traits that are mainly genetic and casts them aside if they aren't seen as desirable enough. As for what the cut is, well, it's many-faceted, but the waterline is rising and as you age all of your desirable traits are fading. If you have real personal relationships (either career or friendship-related) you've escaped it for now, but if anything ever happens to reset your network and cast you back into the default pot, you might get a chance to experience it.
Sure it's not necessary when you produce throwaway code.

Most startups do exactly this.

That's even a valid strategy: Concentrate on the business case only, redo the code when you get successful and have the money to rewrite everything. (Of course quite some companies misses of missed the right time to throw away everything and rewrite it. This results later on in a huge and very expensive PITA; some of the companies affected even started to build their own compilers and static checkers for the languages they use; just look who pays for static type checkers for Python or Ruby).
Oh sure, and I wanted a battery of some kind to keep things running in an outage. I just mean I don’t know why they bid a Powerwall specifically instead of some other battery system.
I love it when people reference "my country" and don't say the country.
> If there’s a mistake in the indentation it’s harder to determine intent.

If there's an indentation mistake in an indentation sensitive language, then there's a mistake. Why does intent matter? Intent is lost because there is a mistake.
each to their own - just highlighting the target market of this website
jesus! https://github.com/microsoft/Recognizers-Text/blob/master/Ja...
I have the GitHub app on my iPad, and at time will review (smaller PR's) from my tablet while not at my desk. Its fine, but for larger PR's or PR's I need to leave more longer more in-depth comments on I will go back to my desk. Maybe I could carry small bluetooth keyboard, but at that point I might as well just undock my laptop.
Apartment and home owners also collude to exclude renters with bad credit and criminal histories, artificially creating a captive market for those people to rent on the constrained supply of trailer lots. Without such pressures I doubt their rents could be so high.
DynamoDB White Paper (2007)
No as I haven’t lost power since installation. However during a power outage I can configure the SMA inverter to detach from my breaker box and operate a single 15Amp outlet
We can start with the fact that German nouns (e.g. job titles) have a grammatical gender. Due to that offers included "m/f" in the past. Since this[0] ruling companies prefer to be safe.

So in short: legal safety and following the German law [1].

That's why German based companies include "all genders" or "m/f/d" in their job listings.

[0]. https://www.bundesverfassungsgericht.de/SharedDocs/Pressemit...

[1].https://de.wikipedia.org/wiki/Allgemeines_Gleichbehandlungsg...
Yeah. These folks should probably hire a designer. They clearly put a lot of fancy looking elements in it to attempt to replicate the look of a designed page, but that's not how it works. Many developers think design is like air freshener for a page-- an aesthetic improvement based on personal preference and taste that's distantly secondary to the real content. But colors, relationships between elements, placement of elements, and all of those things communicate about your product. If they're inexpertly or sloppily put together, it communicates that your product is inexpertly or sloppily put together well before they visually parse your copy and screenshots.

Here's a free first impression breakdown for them: A page's social media link stripe is commonly at the bottom of the page as a final "ok you're not going to buy this right now, but at least keep us in mind" call to action, or at the very top of a page as a nav element. Gray is a common color for page terminal stripes or other perfunctory, de-emphasized components because nothing stands out against it as much as it would stand out against something else. Pricing schemes are either on a standalone page or at least after some introduction explains what they are. Seeing the gray stripe of social media links under the pricing block is like a stop sign to your brain. Beyond that, the "more options" button at the bottom of the page only reveals more options at the top of the page. The section of tiny screenshots half covered up with those boxes in that same "not important" gray is very off-putting. Not only does varying shades of gray text on white or various shades of gray background scream "don't pay attention to me," it's irritating to read, and their #969696 text on white on the purchase page even fails WCAG AA color contrast guidelines for headlines. Many elements are slightly misaligned. The complete lack of visual hierarchy beyond the project name and purchase section title leads users to subconsciously say "not worth the cognitive load to figure out what's going on here," and leave... and that was a sub 5-minute analysis.

Most bounced users don't consciously think about why they left. They'll never complain about it because they'll never think about you again. There's a damn good reason big businesses put a lot of time and resources into that stuff, and as much as folks like to think otherwise, having developers as your customers doesn't change that. Developer-targeted FOSS projects get away with undesigned websites because it's free as in speech, and most people are probably looking at the very thoughtfully designed Github, et al interface instead. Even subconsciously, broken buttons, misaligned elements, uncomfortably obfuscated elements, and miscommunication of navigation cues through poor color choice does not communicate "high-quality paid software product that beats the vast array of free competition."
It doesn't necessarily fix it but has less resource waste or is easier to manage than the bin packing needed otherwise.
Learn WebGPU for C++
I think you are making some really good points, the fact that the bulk of the initial bugs were found by users and not by the developers is what caused initial adoption of V3 to run into an immediate roadblock. If that had not happened the whole thing might have gone over a lot faster but it caused a lot of people to go from 'Yay, UTF-8 strings' to 'wait and see and let someone else handle the bugs, we'll check back in a year (or two, or five)'.
none of what your suggesting is technically challenging to setup for a small org, scale it up to 10's of thousands for some companies, or more..

Plus its almost NEVER up to the tech people to deploy whatever they want, someone at the C level got a sales pitch for a given product, liked it (may have even gotten commission or a kickback) and told you to install, setup, support given product(s). or in my situation Infosec told the network guys to implement X and it breaks everything at the user level...

and your end users will hate you if you reinvent the wheel for every internal product/process... things like Jira put a ton of that kind of thing into one interface, under one user - preferably with single sign on.

your v1.0 of a given product will never be as easy to use, or well thought out as v10 of another vendor's product doing the same thing.

And those companies take care of regulations, scalability, and can even help with audit findings - not to mention gives you someone to blame when things hit the fan.
Looking forward to the performance per watt on these babies.
> they'd still be subject to GDPR and other related privacy laws

Just like they currently are breaking the law by using non-compliant data processing consent flows (90% of the "cookie consent" flows you see out there don't comply), and how they broke the law for over a decade before the GDPR (turns out GDPR had prior art in most EU countries)?

GDPR penalties are not enforced anywhere near enough for it to be a deterrent.
The Future of Micro Frontends (2022)
The key of the idea is you're not asserting that predicates on values are true, you're recognizing whether a value (of a type with few guarantees) conforms to the guarantees of a type (implicitly, a type with more guarantees), and transforming the value into a value of the output type.

Parsing might not be the right word, but it's definitely an example of the above; we transform a string into a tree of tagged nodes.
Why are the leases so problematic? If you don't have the funds nor credit score to finance it, why not just rent out the roof space so to speak? Any return you get from it is better than nothing.
Yes this is what I meant.

The way Azure does it is kind of nice (to me at least, as an ex member of ARM) because ARM can generically check access just by the URIs. The downside though is that the URI also includes the subscription and tenant id, so ARM has to deal with the URI being stale after stuff gets moved around. And then the advent of management groups and cross-tenant access made it so it's not quite so straightforward anymore. But it was still quite useful.
Excess sent to the grid using the NEM 2.0 TOU-C rate plan.
Why do you need this pain?
Which paper? The one pointing out that links are easy to determine with only a small genetics database? Why would I care about that, I want law enforcement to have (audited) access to 100% of the populations genetic records, so I'm not concerned about how small a sample is needed.
Half of the large apartment complexes in my city are owned by the same corporation. They don't even have to collude to set rent, because they are all the same entity.
With what media platform would Russia "shout it from the rooftops" to Western audiences? Who would listen?
> 3. "Full Self-Driving" is either a delusion or a swindle, and the continued insistence on it puts me off the brand.

I think FSD will happen eventually.

What people don't understand is that if you buy FSD now, you're not paying for a feature you get now, you're paying for a feature that you'll get later as it's developed. You're paying for early access in the beta. Also, Elon has stated that the price of FSD will increase over time as it improves. By buying it now, you're insulating yourself from future price increases.

That said, Elon's marketing of it is pretty deceptive. He talks as if it's only 6 months away, but you'd have to have had your head in the sand to not notice that he's been saying FSD is < 6 months away for YEARS. If you're spending thousands of dollars on a feature that seems very pie-in-the-sky, then I would hope you'd do research on it first. Even just 10 minutes of research would yield a conclusion that FSD isn't there yet and won't be there for several years.

If it matters at all, I've been a Tesla owner for 3 years, did not buy FSD, and will not buy FSD. Autopilot is all I need.
> It has huge adoption in the RonR community

Is that even true? DHH (RoR creator) hates TDD.
> If it's the latter, then reduction of 1 kWh delivered should save them the same amount of money.

The "net metering" policy being changed isn't regarding "saving the grid the money by reducing the amount delivered to a customer." If you don't use the power from them, you don't pay for it. But this is about the utility paying the customer the retail rate for excess generation - aka paying retail rate for something that would offset a cost they'd otherwise pay wholesale rate to generate. This is about the current (not the new) system: https://news.energysage.com/net-metering-2-0-in-california-e...

It's not clear to me at all that it makes sense to compel the utility to purchase your excess power at the retail rate, if you're generating more than you can use. It also seems to gives weird incentives to size and spend on your home setup.
But impossible to get hands on supply, or am I missing something?
I do want one but:

1. my 2012 car still works
2. Stopped driving in the pandemic
3. not sure I can go full EV yet

I am looking at Hybrid minivans though
Disagree: great (non-fiction) writing should provide information in an efficient and structured way, so that readers can quickly understand the key points and if reading further is worth their time.
That's how my distributed generation contract with our Rural Electric Cooperative works. We pay $50/month for the connection, but the actual use/generation is 1 for 1 net metering. We are limited in how much generation we can connect to 105% of our average annual consumption, so over the course of year, on average, we zero out energy costs. If we want to connect more distributed generation than that, the tariff shifts to we get wholesale for what we sell, pay retail for what we use.
https://projectsolar.com is another DIY-able option, where they help with the permitting, etc.
Do note that this project isn't open source: for something like an editor, this is a bit of a negative for me since it significantly reduces how it can be customized if need be.
Calling the police is totally an emotional response.

You made a business contract with a company. In that contract, they stipulate that under certain circumstances they will hold your money. What is a problem is the company is completely full of shit in how they handle these situations. They are "protecting themselves" from your account potentially being some sort of fraud. This is all automated with zero to little human involvement which creates potential for lots of false positives. During these cases, the company is 100% at fault for being cheap ass bastards that show zero sympathy towards users.

This is not something for local police to be involved. The disconnect seems to be emotional vs logical.
If "Readings in Database Systems" is your cup of tea you should probably consider

* Database Internals (https://www.oreilly.com/library/view/database-internals/9781...) - very recent and of manageable size

* Database System Concepts (https://www.amazon.com/Database-Concepts-Abraham-Silberschat...) - specifically, the chapters on storage and query processing, it's a huge volume otherwise. Also, "Database Systems: The Complete Book" is basically an older version of it.
> We all know what the medical profession quite rightly thinks about patients who turn up having (supposedly) self-diagnosed themselves with the help of Doctor Google.

And we all know what artists think about AI art...they hate it, because it's pretty good and it's going to take a lot of their jobs.

"Doctor Google" is pretty bad but there's absolutely no reason AIs can't get very good at most areas of medicine. For now doctors don't like Google because it gives bad results, but pretty soon they're going to start hating it because it gives good results.
Yes, that price is insane!

I don't have A/C, do have net metering and do have solar panels, so I intentionally picked the plan with the highest costs during the day in the summers and I pay 24c/kWh only in peak hours during the summer.

Author may be a high energy user and on a tiered monthly-usage plan rather than a TOU plan; if that is the case than the solar panels may be saving energy billed at the highest marginal rate which might be 25c/kWh. My previous house had in-ceiling electrical resistive heating only and I accidentally got a 4-figure electric bill the first January I lived there because one thermostat was broken. IIRC everything after the first NkWh (where N was a crazy high number) was billed at around 25c.
Some one-instruction machines are surprisingly code-efficient.

Consider an instruction with four fields: A B C D. Words and addresses are normal two's-complement integers. Every cycle, the machine takes the value at address A, subtracts the value at address B, and stores it in address C. If the result of this, as a signed integer, is 0 or negative, it jumps to address D. Otherwise it take the next instruction. Using temporary values in RAM, self-modifying code and some constants, everything can be implemented with this single instruction. And a lot of it surprisingly efficiently. Some assembly-style syntax for such a machine:

A B C D
#0 #0 tmp destination

Jump to destination. 0 - 0 = 0, so jump to D. The # is syntactic sugar for an immediate literal. The value is placed in an address and that address is used. Tmp is a memory address, a temporary scratch value. In my made-up syntax here this is implicit if there's no 4th field given:

// move is simple
src #0 dst

// subtract
srca srcb dst

// negate
#0 src dst

Addition is an exercise left for the reader :) Let's use * as the current address in the program, known at compile/assembly time. We can do a cheap subroutine call:

#0 (*+3) retaddress subroutine

Negative of the return address of the next instruction is in retaddress. Result will always be negative for sensible addresses, so jump to subroutine. To return, just write the negative again back to the D field of an instruction:

#0 retaddress (*+5)
#0 #0 tmp tmp // last field will now have return address, jump

Of course, writing self-modifying code without checking it is guaranteed to not work. I probably got the offsets and stuff wrong. But hopefully it gives the idea. Doing the same with the address fields lets you do arbitrary indirection and address calls and make a stack. Often 2 - 5 instructions. Everything a typical RISC machine can do can be done in 1 - 30 instructions. Except multiply, divide, and bitwise boolean operations on the whole word, because you have test and branch on each bit in an inconvenient way. I'm sure something more efficient is possible, but it's quite an improvement on the classic subleq code density.

One-instruction set computer: https://esolangs.org/wiki/OISC
Most Indian government bureaucrats won't understand tech. Court judges are even worse; not only will they not understand tech, but as unelected officials they don't even particularly care about the economy, and are accountable to no one but themselves.
Why would I? I’m on NEM 2.0. The grid is my “battery”. Every KWh I generate that isn’t used is sent back to the grid. In exchange I get an IOU for the equivalent $/KWh price during that time. This is the retail $/KWh which includes transmission costs.
It isn’t - other customers are paying for their ability to have electricity when (and how much) they want it, via the net metering subsidy. If you divide their cost by the lifetime expected generation, you get 9-13 cents per kWh depending on panel subsidy. This sounds great in California but isn’t far off from retail prices in some states. And the actual grid “wholesale” price is usually far less than that except at peak times or exceptional situations. You pay at retail to still have power in those situations. With net metering everyone else pays you that price for something you are not providing.
Except that there really was a time when a person was able to graduate high school, go down to the local factory, and get a job that would buy a house and support a family with nothing other than a firm handshake. They didn't do it on a McDonalds salary, but that's because this all happened before McDonalds were around, and the cafes and restaurants that McD's later replaced all paid living wages.
I see this as an AM/FM problem. If one of these disasters happen, then we should rely on "actual machines" to mitigate or avoid them, and not rely on "F*ing Magic" like interplanetary colonization.

I'm not saying we shouldn't try to expand what's possible with "actual machines", but that should be up to academia - and they're pretty clear that human space exploration isn't worth the money.
Wake me up when we get some transparency on what's backing all those Tethers or whether Binance is solvent or not. It's one thing to document scams after the fact, it's another to have mechanisms to identify them before they grow out of hand.
This cannot be emphasized enough. The top of the line configuration you can get today is a dual EPYC 9654. That nets you 384 logical cores, up to 12 TB of RAM, and enough PCIe lanes to install ~40 NVMe drives, which yields 320 TB of storage if we assume 8 TB per drive. All for a price that is comparable to a FAANG engineer's salary.
“Internet in Space” Will Transform the Satellite Imagery Industry: Part II
How often are you opening projects?
I'm creating a 3D claymation fight between Ruth Bader Ginsburg and Amy Coney Barrett done in the style of Celebrity Deathmatch. I've finally gotten enough Blender modeling, rigging, animating, texturing, materials, and video editing under my belt to start producing whole animations. It's going to take months, but I'm confident I can make it happen.
What emotional tone did you arrive to? If "bearish" is your take away I think you should read it more carefully.
I'm an alum of the community (though not of this specific grant). Unlike members of other communities I've been part of, most at SPC have quit their jobs and are all-in to whatever their goal is (research, side projects, or building a startup). Everyone's curious, talented, and want you to succeed. The in person element (if you're located in SF or NYC) helps a ton.

Happy to answer any questions about SPC as a community.
> why all the pearl clutching?

My vehicle has a cellular internet connection that I cannot easily disable. My insurance company is among the many that would love to get at that data. TV's are valuable enough that such a connection will be coming to them too eventually.
Only in "fixed do" version though, because we can't make music notation too easy or consistent...
and server boosts
Location: Accra, Ghana
Remote: Yes
Willing to relocate: Yes (I may need visa sponsorship)
Technologies:
* HTML | CSS | Javascript
* React,
* Vue,
* NodeJS,
* Express,
* MongoDB,
* SQL

https://github.com/kafui4k Email: kafui.alordo@gmail.com
About me:

- Full stack developer with 4 years of experience building applications for the web and mobile.

Open for full time engineering position - frontend/backend | fulstack
For their next-gen Fleet IDE though, it looks like Jetbrains is using Kotlin and Skia/skiko?

* https://blog.jetbrains.com/fleet/2022/01/fleet-below-deck-pa...

* https://twitter.com/jetbrains_fleet/status/14653112312717393...

* https://github.com/JetBrains/skiko
That’s a really interesting question (on code density) - can you share your conclusions or even your project?
This article comes across as muddled, bullshit, editorial piece arguing against privacy and that we should trust corporations. They seem to be naive and not have much real life experience while pushing a position that's indefensible. They're a tech consultant and speaker, so that's the position they're pushing.

---

PS: Actually, I prefer the fork of Signal, Session, because it doesn't require the metadata binding to a phone number.

https://getsession.org