skysight-inc/HackerNews huggingface dataset:
It's a good post but IMHO does still conflate several things. The problem with "gamma" is that it's such an overloaded term.

1st. Human vision is not linear but is more sensitive to changes in low brightness conditions where a small change in input results in large change in perception. This is the so called "Stevens power law". The blog calls the perceptiply linear gradient ramp "gamma encoded" when it's really just adjusting for the non linearity of the human vision and employs "inverse of Stevens power law".

2nd. Because of the human sensitivity to differences in dark tones, a linear encoding when using limited bandwidth (i.e. 8 bits per color Channel) would allocate too many bits for the bright colors (that humans can't distinguish so well) and too little for the dark tones. The normal scheme is here is to encode the image using a "gamma" function that allocates the bits in a non linear fashion. This isn't often a simple gamma per se but a color space such as sRGB but the idea is the same.

3rd old CRT monitors had a characteristic behaviour so that 50% of input signal strength would not result in 50% of light emissions. this non linearity was also called "gamma". Modern LCDs etc panels then replicate this functionality for compatibility purposes.

However I believe the software/display circuitry these days correct for the display gamma so that if you write 0x808080 you'd indeed get 50% of light emission from the display. That means that the 2 really sort of interesting "gammas" are the encoding/decoding for storage and for producing changes in brightness that the human vision will perceive linearly.

Ps. I find that because of this overloading of the term gamma there's a lot of confusion and often if the result is correct it's by accident. I in fact prefer to call the whole thing "gamma incorrection" rather than correction since it's almost never correct in the whole software stack unless by accident. ;-)
Write a book and pitch it to the network. Could be fun. :)
Do you know what a "push poll" is?

Carbon taxes or policies that are basically equivalent have already been used in a variety of political systems across the world in various contexts and have worked well and are popular. Usually, it becomes quickly obvious that simply not emitting the CO2 in the first place is the cheapest option.
It is nonetheless a society wide problem, regardless of individual autonomy.
Start smoking or start smoking again?
It strikes me that this is from the Guardian and I know nothing about UK housing policy. Is anyone here able to comment on any relevant differences between the UK and US when it comes to housing?
This is like the easiest thing for a compiler to detect and optimize.
Bash-Modules 4.0
Balance, or the lack thereof, is one of the most common pain points for the juniors I've worked with.

New college grads can really struggle with finding balance after transitioning out of college. The undergrad environment has well defined start and end points for each class and everyone gets the same or similar workloads, so it's possible to calibrate off of peers and consult with advisors or mentors who have gone through the same system.

Not so with the working world, where there are always more objectives than time and you can't always look to peers to calibrate your progress. Ambitious juniors often see this and decide to go all-in, working as hard as possible on as much as possible for as long as possible.

This leads to burnout in some, though not all, of the people who get swept away in it. We read so many articles about burnout and recovery from burnout that the topic of hard work evokes strong reactions online, as evidenced by this article and the comments section. However, as the author points out there are multiple sides to this story. Hard work isn't always bad, especially if you find yourself enjoying it and learning a lot.

If I'm being totally honest, working hard in my early career paid off significantly down the road. Not necessarily in immediate dollars paid out by my employers at the time, but the network, reputation, and skillset I built along the way are extremely valuable to this day. I didn't even hate the hard work or long hours at the time, because I made a point to surround myself with peers I liked and work I enjoyed. I also made an effort to get plenty of exercise and social activity, which can't be neglected.

In my opinion, too many online discussions around burnout are centered on the idea that work is inherently bad and something that should be minimized as much as possible. An understandable reaction from authors who might be burned out, but framing everything this way has an unintended side effect: It normalizes the idea that work is inherently bad, and that hating your work is natural. This mindset tends to trap people in jobs they hate at companies they dislike with peers they can't stand, all because they've been led to believe that this is the normal state of affairs. They focus too much on trying to tolerate it and manage their borderline burnout instead of trying to move their career in a direction where they can find a job they like.

In my opinion, we need to stop framing this as a debate about whether work is good or work is bad, and start talking more about finding a healthy balance and working toward jobs we like. No job is going to be fun all of the time, but if you're hating every hour of work and counting down the hours to the end of the day every day then you're probably in a below average job.
Cristiano Amon Takes over as Qualcomm CEO: Reiterates Focus on Custom CPUs
God that would honestly be a dream come true actually
> my life improved substantially.

then Maybe it has something to do with you?
Surely some articles have a slant, but to assume that the vast horde of Wikipedia contributors are all 'leftist' is just absurd. Wikipedia is doing a great job overall at getting facts across in a neutral manner - if you have the feeling that's not reflective of your viewpoints then you could either question the source or you could consider whether your viewpoints do correctly fit to the facts. It's very easy to dismiss sources that don't fully agree with your views, but that prevents you from ever strengthening or improving your views.
But then you would need 'unbreak' or just 'goto' to the next case. No duffs device no cigar.

Probably a module/namespace system would be the biggest improvement.
It's great to see a story about people not getting sexually assaulted at Ubisoft.
If you go to Preferences > Misc, you can control which exposure the histogram controls.
> The software industry (SWIND for short) is a mixture of unsafe tooling, high-risk practices, sloppy execution, and total delegation of responsibility. So I agree that the SWIND will never be civil engineering. ^_^

I interviewed a bunch of civil engineers for a journalism project earlier this year, and my main takeaway was never walk over a bridge. We're not that much worse than other branches of engineering in our tooling and practices.
Do you accounted the zarist backwardness from which the USSR started and the incredible WWII destruction in the USSR territory in lives and buildings?
But they do use them? I'm not sure what your comment is supposed to mean.
I really empathise with your experience of lockdown- Covid has taken a big toll on a lot of people, myself included.

Especially at the start of lockdown, I developed a habit of working on a side project at the weekend. I found myself slipping into this 'discomfort', and after some reflection decided it wasn't helping me. I work hard enough during the week, if I'm working outside my normal hours it needs to be because I want to, not because I'm pushing myself into it.

Don't worry too much though- lots of things will change up as Covid eases, and you'll get a load of opportunities to reset yourself. You have an advantage here, in that you built the habit in an artificial environment- the return to normality should help you shake it, if you want to!
Indeed, there is a reason why commercial projects and corporations avoid GPL like a plague.
> Highways need to be completely rebuilt every 10 years.

This is completely false. Even just repaving usually has longer schedule.
Seems like kind of a wordy name, why not just "nonce"?
I love to use phony make recipes to package small bash scripts
Surely the spread north would not have stopped at the border, as well.
> Are you laundering 5 lines of code? Probably fair use.

The amount of copying does not matter for a copyright claim. If you copy a single character from a codebase that could could get nowhere but there, and lawyers could prove it, that could go to court. This is a hypothetical but this is entirely possible. There have been copyright cases fought over single sentences especially in the music industry.

> Are you trying to launder, or is it unintentional?

I'm not a lawyer but in the US, Copyright is a strict liability statute which means intent does not matter.
People go to the ER because they don't want to fuck around with situations that they know they are insufficiently trained to diagnose. When your child is bleeding out of their face why in the world would you roll the dice at the local strip mall urgent care when there is a giant children's hospital nearby? Why didn't the ER send a nurse out to triage this after 2 hours of waiting to say they could get sufficient help elsewhere?

My experience with ERs over the past 20 years largely mirrors that of GPs. Then when we started going urgent care out of frustration we ultimately got inferior care for my wife that delayed a cancer diagnosis by 3-4 months.
In the case of weight loss, just knowing that regaining weight is likely is very atypical. Most dieters labor under the delusion they will be part of the 3% that can make a permanent change. I don't think that's de-motivating a considerable portion of people from making the change.

I do not believe the status quo bias is learned helplessness. I believe it is the natural state of most people and that rational agency is an outlier. We are, as individuals, extremely predisposed to just doing what we do and discounting alternatives.
> when they ditched support for 32-bit software

This has nothing to do with the false claim about restrictive APIs.

> If you're looking for a true Unix box, you're shooting yourself in the foot by buying a Mac, especially today.

This has nothing to do with the false claim about restrictive APIs.

> "the hacker" wants a suite of coreutils that are updated constantly. They want a package manager and an extensible system. They don't want their computer to second-guess them, and they don't want a large corporation to decide what's right for them.

This is an ideological statement that has nothing to do with the false claim about restrictive APIs.

All of what you said may be true, but it doesn’t make the claim about restrictive apis any less false.
I agree with many of the sibling comments, static vs. non-static is almost a complete red-herring.

Static only means that the variable is local to the translation unit (the C file). The relevant difference in the example is actually the const-ness of the variable, which you may put explicitly, but which a powerful compiler can also infer here in the static case.

Other than this optimization possibility, const and static are orthogonal concepts. I'm not sure to what extent the article author is aware of this.

So the lesson should be: use const (or #define) if you mean to have a constant. It's still a good idea to also make things static, but the real reason for that is to avoid name collisions with variables in other C files.
Max Hawkins: I let algorithms randomize my life for two years – Ted Talk
On the contrary, OS X had first support to Java via the Java Bridge and Apple's own JVM implementation, because they weren't sure if the developer community educated in Object Pascal and C++ would be willing to touch Objective-C, so they decided to play safe with having Java for the ride, doubling down on Java uptake.

Objective-C was embraced by the developer community in such a way that they quickly deprecated Java Bridge and eventually got rid of Java development costs altogether.
There is a difference between capitalism and materialism.

The former is a Western cornerstone; the latter is the crass idolatry that renders contemporary culture a disaster.
Best Computer Security Related Twitter accounts you should follow in 2021
> Such houses, the wrong houses on the wrong sites, won’t bring prices down.

Yea i don't quite understand how that be.

Your comment seems reasonable to me but is down-voted here. So i guess we are missing something here.
> You haven't provided any concrete evidence.

Actually, I did. Snipping it from the replies and ignoring doesn't, in fact, make that evidence go away.

Whereas you have provided exactly zero evidence for your claims, except for repeating your opinion.

>What do you mean "works"?

It gets the job done effectively and efficiently. Caper Jones found half the effort to implement the same function points in Smalltalk vs. Haskell.

> FP has matured a lot in 30 years.

Not really. Still the same hyperbolic claims, and still the same meagre results.

> [OO] has all the problems I have tried to articulate previously.

No it doesn't, and just repeating an opinion over and over doesn't turn that opinion into fact.

> [Frederick Brooks an academic] Does it matter?

If it doesn't matter, then why did you bring it up? Oh right, to dismiss his widely cited article that you yourself referenced as "just one academic's opinion". Well, he is not, in fact "just" an academic, but has more practical experience with software than most people on the planet, including you and me. He is also an academic. So someone with vast amounts of industrial and academic experience and expertise.

> keep the debate civil.

It would have been nice had you done that.

Anyway, it is clear that you aren't interested in evidence or reasoned debate, so I think we can call it a day.

Have a good one.
FWIW: Go's switch statements are break by default, with an explicit 'fallthrough' keyword if one wishes to override that behaviour.
Bear Notes, the popular note taking app for Mac, stores data in sqlite for many of the same reasons the author mentions here.

Bear organizes with "live folders" based on tags added to the document, powered by sqlite.
Which brings us back to the article’s point of manufactured demand.
99% sure that Nat Friedman is wrong there.

He's correct that AI can train, but it's not relevant.

(1) The issue is with CoPilot outputting copyrighted code AND attaching a separate license to it (looks like it's hiding the initial license and can generate another license automatically). This is reproducing copyrighted code and misrepresenting the license, neither is allowed.

(2) He posted that the output belong to the operator. It's factually wrong. Original copyrighted code belongs to their original writer, not the operator. In effect Github Copilot cannot "launder" license and it is very wrong for their CEO to claim otherwise.

(3) Looks like he's trying to waive responsibility of Github by stating that the developer receiving the code is responsible? Wrong, GitHub is responsible for their actions (vary with the jurisdiction). There's a complex matter of who's responsible when some proprietary code will end up in a company product and they get sued. The company is in violation, they can turn against GitHub for providing copyright code, GitHub was responsible for it. There's a complex chain of responsibility, any lawyer worth their salt would cringe at the claims and responsibility that GitHub is exposing itself to.
Compared to your aliens, observing the entire history of earth, 400 years is relatively short.

You keep comparing the colosseum killings to events that transpired over large geographical areas, for different purposes than entertainment. As me and others here have pointed out repeatedly, what makes it special (to us, not to you apparently) is the fact that all those killings happened on a single location.

You cannot measure how primitive a culture is by the amount of people they kill.

To me (and, I would argue, most people), the monument symbolizes specifically those often pointless killings and nothing else. That is what it is famous for.

Unfortunately, your replies regularly border on the insulting. You keep pointing out how the arguments you present are things I "fail to understand" or prove my lack of knowledge of historical events, often telling me to "go read a book", like I'm some rambling child. Meanwhile, you have not told me anything I did not already know.

I'm done with this discussion, as it does not appear to go anywhere. Good luck with your opinions, I'll hold to mine.
Maybe a bit off-topic, but I noticed that https://www.sqlite.org/cpu.html hasn't been updated in over two years and given the consistently high development speed I'd be curious how the "CPU Usage" deals with all the new features. :-)
> Nobody ever told me to work late, but nobody ever told me to _stop_ working. If my boss/bosses boss/<etc> came up to me a once or twice and told me "hey, you shouldn't work past <x> PM", particularly in my first few days, _and most importantly_ they left too, that would have set an excellent example on how to have a work-life balance.

I've had managers try to nanny my working hours like this. It wasn't fun. I know they thought it was a good gesture, but if I have a spare hour or two in the evening and a good idea I want to try out before bed, I don't want anyone telling me I can't work right now.

In fact, I don't want my manager policing my working hours at all, in either direction.

What works better is for managers to gather honest feedback about how long tasks took and how many excess hours were being worked during their 1:1s with employees. It's not hard to ask employees how their workload looks and adjust schedules or resource allocation to compensate.
Either they have a brilliant plan for accelerating capitalism until its breaking point or the party cares more about staying in power than about their ideology. We can only imagine which one it really is!
It's a great illustration of how celebrity is leveraged by the powerful. Muse group picked tantacrul, a celebrated figure for his strong opinions, and told him, "here's how you can do good." And he can do lots of good, but this isn't a tasty way to do it. This is using him instead of as an experienced ui consultant in music software, as a smokescreen for an exploitation of open source culminating in sending user data to Russian law enforcement.
This is why language standards specify what the compiler can assume and call out some behavior as undefined, exactly so compilers don't have to be paranoid and produce code that sucks. If an underlying object is const, the compiler is allowed to assume that it does not change (it is valid to cast away const on a pointer or reference, but not if the object itself was declared const).
Would this in general be true of any attribute that is significantly skewed? I.e., if you remove someone at random from a pool of n individuals, it's more likely to be someone at the lower range, and so the remaining (n-1) persons will be higher on average?

I'm also reminded of the paper making the rounds a couple of years ago showing that uniform allocation of wealth, combined with simple exchange processes, in the presence of randomness, can lead to very skewed wealth distributions independent of anything else.
Or use velcro, which is even faster.
We’re not even in the “Model T era” of EVs yet. The landscape is still evolving and will become more available and accessible to more people.
I'm gland for this much needed change. I hope it also makes it to frameworks and libraries such as JBoss, ExpressJS.

Idempotency is simple to understand but tricky to implement in practice because of a bunch of edge cases; handling of business failures, response (should it be the first successful response?), how to document the behaviour without confusing the developers and so on. So developers either don't consider it at all or when they do, they forget to consider all these aspect.

FWIW we, as a team, spent quite some time debating and going back and forth; I'm happy with the final behaviour we settled on though the documentation could have been better[1]

[1] https://developer.uber.com/docs/payments/glossary
> My parents use 900kwh of electricity / month and complain that PG&E are ripping them off when their bill is 400$ / month.

Well, in Sweden the price for that would be $160. You seem to be kicking downwards by reflex.
I kind of doubt it is a business decision. It probably comes from a security requirement for Windows Hello or something else. Or it could be from a technical manager that doesn't want to support endless configurations. Either way, I just can't imagine that the backwards-compatibility DNA of MS will let this stay.
@cyberge99 thank you for your feedback and Sorry for this problem, we will fix it. Thank you :)
The way the information is organized can often be just as important. Good data keeping practices can be applied to the history of changes in the software code as well.

The problem is we're still discussing(arguing) over what good practices are.
What I'd like to see come out of this is for corporations to view customers' collected data as a liability, not as an asset. Then maybe they would think twice before collecting and storing unnecessary customer data. Or if they have to collect it, they would expire it as soon as possible. This is somewhat hampered of course by regulations that may require hanging on to data.
They were discussing ways to dilute his shares. Bill tried to buy him out at a much reduced rate ($5 a share). When they went public a couple years later, the share price was $35 on the first day. Either way the whole thing was precipitated because he wasn't being as productive on account of having cancer.
Bill likes to say that the relationship was repaired near the end of Paul's life, but at the same time, he wouldn't take or return a call from him when he was on his death bed, which they talk about in the mini-doc "Inside Bill's Brain".
I think you're mixing theory with practice; DevOps should not be a role, but it often is...

As for requiring another specialist role, that's not the goal of building an automated system. Or at least, this specialist will not part of the team that's building the product, but rather of the company that's building this automated platform. If you can automate the orchestration and management of Kubernetes or serverless, then developers just need to know how to build a container or upload code on a serverless platform.
What exactly is wrong with "scaling" on Linux? I use Qt apps on Plasma and everything just works. Nearly all my displays are HiDPI now.

If you use 2x scaling (or other integer scaling), everything is fine. If you need fractional scaling, things break down pretty quickly, at least on GNOME.

Once you use fractional scaling (e.g. 1.5), GTK applications will scale correctly, but are slightly slower and consume more mattery. However, all XWayland applications are unusably blurry.

Unfortunately, fractional scaling is really needed on 14" 1080p laptops or 4k e.g. 27" screens. With 1x scaling everything is tiny and with 2x scaling gigantic.

The only workaround that worked ok for me was using 1x scaling and using font scaling in GNOME. Many controls and icons are tiny that way, but at least text is readable and not blurry. Of course, this only works up to some extend and when both screens need the same amount of scaling (since font scaling cannot be configured per screen).

[1] https://gitlab.gnome.org/GNOME/mutter/-/issues/566
Yep. They would have had to filter their training data down to the most permissive licenses to be entirely safe. The WTFPL, CC0, and any others that give full "do as you please" permissions.
I have also installed and managed many Linux systems. Doesn’t mean I want to on my main driver. I also don’t want a cheap plastic computer with a terrible trackpad (regardless of how great the intervals are) and until recently, that was pretty much all you could find in the non-Mac laptop world.