skysight-inc/HackerNews huggingface dataset:
If The Drive/War Zone knew this, half the mystery would have been explained months ago.

What a crazy system. You get a bonus if you are granted patents (including your superiors) who then back you up against the patent board that the patents are operable (when they clearly couldn't be).
I remember learning how to get my site to display decently on different screen sizes. I got an abridged history of past attempts: "handheld" CSS media type, then media features "device-height/width, resolution, pointer, orientation, aspect ratio", some people try to use the User Agent, others target a huge list of specific device resolutions, webkit has a device pixel ratio?, it all seemed like a huge mess.

Then it turns out the solution isn't CSS it's the HTML "meta" tag:

<meta name="viewport" content="width=device-width, initial-scale=1.0">

On top of that I use media queries to respond to the font size.

@media (max-width: 35rem)

I'd love to know if there's a better way, but this has been pretty good for me.
Don't worry, the economy in Argentina is back to being shit since over 10 years ago.
Argentina never changes.
We definitely considered using a cell phone to drive position data, but it just didn't get there in terms of my time. Not a huge regret but it would have been nice to feel like I put a technical bow on that project.
Like most tech, I don't think the thing to think about is the lifetime of the device. Really nice headphones that are "vintage"(?) exist, as evidenced by the comments here. Leaving aside the fact that HN is notorious for having a strong segment of nearly any *-phile group...

The question is rarely the lifetime of the device. It's usually the lifetime of the interface. Or in this case, a headphone jack. 1/8", 1/4", etc... This is what normally gets obsoleted rather than the device itself. For headphones, the big switch is from wired to wireless. And I think that's where you'll see the shift. Yes, you can get a bluetooth adapter for traditional headphones, but they aren't great, and if you have audiophile wired headphones, you won't be happy with the sound. And so, the device won't be obsoleted because they fail, but rather the preferred interface changes to something that's incompatible. Maybe audio was lucky that there were adapters available for the first shift from 1/4" to 1/8"...

In this regard, I think the audio world is just catching up to their other brethren in the tech world.
> “Wayland sucks!” is a conspiracy theory with no basis in truth, and its supporters have spent years harassing Wayland maintainers, contributors, and users.

See that "and"? Your comment here only addresses the second half of that sentence, which is probably true, and people shouldn't do that. Most of this thread is discussing the first half, which doesn't seem like it's actually correct. You can't say "people are missing the point" when he's making two points in the same rant.

There are pro-wayland people in this thread arguing the former point ("Wayland works for almost everyone"), and mostly they aren't putting up convincing arguments. So far I've seen: "it's really someone else's fault" (ok, in the meantime wayland doesn't work for me") -- "actually no operating system should support this" (ok, back to windows or apple or non-wayland linux it is).

> More likely, it does work, and you swallowed some propaganda based on an assumption which might have been correct 7 years ago.

> [Wayland] invented some new, fixable problems in the process — most of which have been fucking fixed already, and years ago!

> Most of the lies you’ve heard about ways that it’s broken are just that: lies.

The author didn't support these statements at all (which is the whole point of the rant, he's tired of doing that. that's fine). Someone else has to do that for this rant to make sense. So people are saying, "here is my common use case. how does it work on wayland now?" If they only thought it was broken due to lies and propaganda, it would be easy to explain how it's since been fixed. But people aren't.
* is not an operator in Lisp. It's a function. Lisp doesn't have operators.

To be more precise, cl:* is a function. But you can make a symbol named "*" in another package and define it however you like.
Just a mascot I presume
Amazon is a design garbage bin, but it doesn't seem to be reducing their sales.
This comes around a lot when working with contractors. They are signing up for hourly work for an hourly rate, and generally don't care if what they are executing against is directionally correct. If you say build X, they will go off and build X and the success or failure of that engagement is largely determined by how well and clearly you defined X.
For what its worth, I've seen KN95 masks and N95 masks being in stock from trustworthy retailers at reasonable prices (~$1 per mask) so I picked some up. My layman's assessment was that they did a significantly better job of sealing around the sides of the mask than the cloth masks I'd purchased early on or the surgical-type masks I'd more recently switched to. They also had the side benefit of not allowing air to escape out the top and fog up my glasses.
Chrome has not been receding. Whitespace is chrome. But worse than that it's useless chrome that offers no functionality or visual hinting like skeuomorphic chrome did. Hiding functionality that used to be discoverable through menus behind invisible, sometimes baroque gestures is not an improvement for most people. I have family members who, several times a year, will mute their phone or dim their screen after accidentally bringing up control centre. Explaining what they did "wrong" to them after the fact is nearly impossible - "No don't drag from the edge like that, do it like this."
They didn’t learn much about scaling, the site is down.
I've been in both sides of the table: ran a dev agency in Central Europe, as well as hired developers from various places in the world.

In my experience, wages of experienced developers don't vary so much geographically, because outsourcing is a global market. Dev/agency in Ukraine, Germany, China or Argentina know what kind of rates they can get based on the skillset involved.

These rates are much lower than in superstar cities, that's basic supply and demand and CoL calculation.

But companies chasing extra low rates will end up with subpar team and these are the clients and agencies that give outsourcing a bad name - be it India, Nigeria or Slovenia.

That's not to say rates are flat. Specialized shops/devs, people involved with prominent open source projects and those that invest in deeper relationships with the clients (and delivering higher/noncomiditized value) can charge a premium, while body shops on UpWork will bid lower amounts.

Outsourcing, like many other things in busines can be great IF you know what you're doing.
Pontiac Firebird, they burn and crash allot ;)
An interactive introduction (now unmaintained as author wrote to an HN submission) to X windowing system:

https://magcius.github.io/xplain/article/index.html

That covers the graphics part which is the same for the two windowing systems.
See Wayland's FAQ[1] and architecture[2] page for why it was made and how they differ.

https://wayland.freedesktop.org/faq.html

https://wayland.freedesktop.org/architecture.html

Though not primary goal according to their FAQ, Wayland also improves security.
For this see:

https://lwn.net/Articles/517375/

http://mupuf.org/blog/2014/02/19/wayland-compositors-why-and...
There's all the difference in the world between asking "why do you want to do that?" and "why would you want to do that?"
AllWinner are another one. They are currently doing 5 million RISC-V chips at TSMC, because that'll save them a few pennies per finished phone/tablet.
Yes, I know people do things like that (mostly on Twitter, it seems), but I wouldn't recommend it; it'll interfere with searchability, copy/paste, etc., and generally make the text less interoperable. The mathematical alphabets in Unicode are intended for specific technical uses where the typeface is an inherent part of the symbol's identity, not for styling normal text.
It's not consistent with someone scribbling at random. (See the Codex Seraphinianus for an example of what that looks like.) But some researchers have demonstrated formulaic ways of generating nonsense text with the same kind of characteristics, using methods that were known in the 16th century.

Adding support to that hypothesis is that there is no evidence of any corrections anywhere in the book. If it were real text, you would expect mistakes and corrections. If it were meant to be nonsense, there would also be mistakes, but there would be no particular need to correct them.
I didn't mean to imply that Valve's contributions have not been significant in improving the situation with Wine, only that unlike the other examples Wine was already good before the involvement of a wealthy company.
I like to start on the desktop but build in a way I know the objects will flow. Then I set up a tester with a bunch of breakpoints and check as I go and make micro adjustments to each element that is "off". Then you can set the element inspector to the side and just keep shrinking the screen to make sure nothing is awry as the width gets less and less. I don't really have X sets of 'rules', just elements adjusting at the point it feels right to adjust them.
Open Mission Control and drag a window into an already full screen application. You can also drag two windows in a new full screen space, or drag a full screen space into another to merge them.
https://dayzerosec.com - We do a weekly security podcast on exploit development and related topics/research.

Its a pretty niche target audience so its unlikely to make money or be any sort of object success. But its self-fulfilling; it has been great for keeping me on top of new research and trends that impact my job.
The Garden of Forking Methods
I think his point might be that the level of overdraw with this scaled 2d sprite solution is expensive. The CPU costing model for PICO8's scaled sprite (sspr) function is 2*n (n = number of pixels drawn). So drawing something the size of the screen once is 32k cycles, which is 0.4% of the CPU budget for the frame. Let's say 32 full sized layers, that's still only 8% of CPU budget, so ... yes I agree this doesn't seem expensive even via brute force with no tricks. :)
You should get rid of the AI and do this as a white-glove service to validate _your_ idea.

Just straight up building landing pages yourself, asking the questions, be the AI yourself before spending too much time on building AI you may not need.
Cars changes a lot. Basics do not change, but it's the same for computers to. Keyboard, mouse, display, touchscreen, all this has been there for decades.
Details though do change a lot. Compare the controls of 2 cars, one from the 70s, one from now, I'm quite sure you'll have much more buttons, a touchscreen, things to learn like how to disable airbags when needed, where to get the maintenance information. Even something like starting the car itself is likely to be different.
Ask HN: How do I stay sharp as a developer?
I am noticing that I'm not as sharp as I used to be in the code. What resources/techniques do you use/recommend to keep learning and staying sharp?
my CEO/cofounder is addicted to outsourcing to India. He has eschewed even considering making any first hires in the US because he would rather hire a boutique contractor from an India firm. I think this boils down to him seeing engineers as fungible legos, so the huge pay difference is just a discount on certain bricks.

it's made worse by the fact that a founding team member left the project, so now he is wanting to hire yet another contractor so we don't "fall behind."

i've done my part to explain the mythical man month to him but it's fallen on deaf ears. you'd think the founding engineer of the company would be considered the expert in software project management, but apparently having an MBA trumps that.
Garuda is meant to fill the void between Arch Linux and Manjaro Linux. Trying to be closer to Arch by having only one extra repo than Arch linux compared to 3 repos (Stable, testing, unstable? ) in Manjaro. Some tools shown are of Manjaro origin. Like Pamac & Garuda Settings Manager.

Context:

I am hearing about Garuda Linux in Manjaro forum where I presume "the developer" talked about it in the "Other OS" discussion section. With the deteriorating community relations Manjaro has been having with their community and with some of the Manjaro folks like old time users/volunteers moving to Garuda because of it, Garuda Linux has a place and an opportunity at hand to outshine Manjaro. If they keep their community relationships in check I guess.
Thank you! That's a very valid point and we've seen this with customers quite often: the thought of changing the whole underlying layer can (understandably) scare people.

We've built a (soon-to-be-completely-)automated process of converting Google Tag Manager containers to Zaraz, and that helps a lot with convincing customers because everything Just Works without them needing to do anything (we also hook to their dataLayer events). For other tools it's still a work in progress, but in general we convert whatever stack a customer has to Zaraz as part of the onboarding process. Honestly that's one main reason why we don't yet offer a free tier.
That’s true, but doesn’t solve the underlying issue of X11 security. You can patch some individual holes, but you can’t fix X11 to actually be properly isolated and secure (especially as that’d make compositors and DEs impossible to use).
Gem (YC S17) Is Hiring
https://gem.com/company/careers

Gem is building the OS for modern recruiting. Recruiters, hiring managers, and leadership at 400+ companies -- like Dropbox, Slack, Snap, Pinterest, Robinhood, and Bridgewater -- use Gem for hours a day to automate their recruiting workflows, collaborate on outreach and debug their hiring funnels. We’re also helping our customers track and measure diversity for the first time throughout the entire hiring pipeline and stay accountable to their goals.

We’re a customer-driven team where engineers have a ton of influence on product strategy and business decisions. We take calls with customers, own features from ideation to launch, move with velocity, and make it our mission to delight users. We don’t shy away from tough technical challenges, but we believe in technology as a means to an end rather than an end in itself. If this sounds like your kind of team, we’d love to hear from you!

More about us:
https://www.gem.com/blog/what-its-like-to-work-at-gem
https://medium.com/gem-software/what-product-engineering-mea...

Tech stack: Python, Flask, AWS, React, GraphQL

Apply at https://gem.com/company/careers and feel free to email us with any questions at nathalie@gem.com
Modern-day honeypot?

Aight imma head out.
It's easy enough to see what the money gets you in Ukraine, since developers there are paid in USD or EUR anyway. And the outsourcing company takes a big cut of what you pay.
Workflow Engine is a tool for you
There's nothing new on the front-page, and Gentoo has been around a while.

Curious what the motivation for posting is. I suspect the HN readership has a good idea of what Gentoo is.
Weird social effects of being online:

If we were in a room of 100 people, and two folks got into a shouting match, everyone would start listening. And then a group decision would get implicitly made. Is it a personal argument, best to stay out of it? Or is someone getting attacked unfairly, and it makes sense to intervene? Everyone in the room starts watching, and everyone starts thinking about what the group is going to do.

Online is nothing like that. If someone behaves like a complete asshole on one thread, most people don't see it. Especially if the asshole is "some random guy" with no standing in the community. Since there's no real drama, the incident doesn't come to the community's attention. The person on the receiving end of the abuse never gets to have that moment that you'd have in a room of 100 people, where you know everyone sees you and supports you, and maybe you get some "points" for keeping your cool. There's no points for that online, just silence. I think it can feel very isolating and frustrating, and I'm not sure how to address it.
Yeah, I thought the post was already too long to also talk about Signal!

My opinion on Signal is it should definitely be preferred if one cares about security more than usability. I really cannot wait for it to have a "standalone" client (that is, that does not require the phone to be online as well).

There are other messaging apps, like Element (and the now defunct Keybase) which try to solve the same problems. So, I decided to keep that discussion for another future article (maybe).
Ok, here is my use case that wayland doesn't work for. I have an AMD graphics card (5700xt) and two 4k screens. I want to run firefox, chrome, emacs, and a terminal.

Using KDE or Sway, if I set my desktop scaling to 2x, all programs that run through XWayland have extremely blurry display (they've been rendered at 1x and then crudely scaled up). This includes firefox, chrome, and emacs. The browsers have ongoing work to support wayland natively, but neither is stable for me.

If I set my desktop scaling to 1x, I can then scale up individual xwayland programs with flags like `--force-device-scale-factor` if they support them. This gets me close to the behavior on X but on X I can just set a global 2x scale.

I totally understand the frustration of OSS maintainers when people demand they fix things with no intention of getting into the code. On the other hand, the marketing behind wayland encourages some unrealistic expectations. I went out and bought a new graphics card and it turns out I can't even run firefox! That was not what I expected to happen.
> I can't imagine RISC-V beyond niche applications unless someone publishes a more strictly specified version of it that provides a unified platform.

What do you think `RV64GC` is?

RV64GCV, RV32IMAC, etc are all short-hand describing the supported capabilities of a given RISC-V CPU.

ARM has different specs for each type of core. https://en.wikipedia.org/wiki/ARM_Cortex-M

Compilers have handled this for years.
YC Build Sprint Winter 2021 – Get feedback on your YC application
Sounds good. I know that feeling. :-) Cheers.
I've never heard a small content creator say anything good about the DMCA; all I've heard is big content abusing the system to claim the work of small creators.

Also, the entire premise of your DMCA example for small creators is false and trivializes the difficulty of even finding violations. "Google searches are free"? As if I can spend 5 minutes google "who copied my stuff"?
A quarter of a century ago is... 1996. Not the 80s or whatever you're thinking.

But what's that got to do with headphones?
I'm a bit confused about your post.

Why would Xorg users care about XWayland, or new releases or contributor patches?

Those who contribute to Xorg and feel stuck could step up to maintain it, if they wish. (Don't they do it already?)

If they don't wish to maintain it, maybe their contributions are a waste of everyone's time? (Then again, maybe they get paid to do it, in which case it's their money-misery trade-off to make.)

Over time, Xorg users may indeed need fixes. Then, I'm sure someone will step up.
The types of companies that a remote-first world needs (Techstars)
My dad’s Sennheisers from the 1980’s still work well. They have the huge plug, so we have the adapter on it, but otherwise works fine. Foam had to be replaced once or twice, but otherwise it has surprised me how long they’ve lasted.
This simply ignores the primary threat model.

Can govt or a company mass harvest chats to classify users into buckets? and use this data to manipulate people. We have seen this happen with Cambridge Analytica. Think of military having a list of all pro-democracy people before staging the coup.
btw, I use Arch
However bad people think X11 is, the engineering decision (or more likely lack of any intentional design decisions beyond the initial extremely narrow use cases?) to "replace" a huge portion of its functionality with windowing toolkits is a disaster for open source. I have written about this before, but the amount of waste and rework that it induces is completely unsustainable. If you want to see another generation wasted in the bazaar then stick with wayland. Wayland is very good at the use case it was developed to serve, which is fast booting systems for automobile backup cameras. Everything beyond that is at best an afterthought. Forcing dbus on everyone to replace xlib is like chopping off your legs because you heard that you can run faster with the new carbon fiber prosthetics -- it will work fine on a track, but the second you try to go hiking off the trail with boulders you will fall and break your skull.
Its incredibly how dismissive people are, and clearly haven't thought about it that much.

> ISA fragmentation ... binary distributions harder.

A overly simply one-sided analysis. You have to look at the cost and the benefits. Not simply say 'look there is a cost' therefore it is bad.

The modular architecture also allows RISC-V to be optimal in many different industries and form factors, from literally the smallest CPU ever created to massive multi-core servers.

The system is designed so that as much software as possible can run on the minimal spec and thus work does not have to be repeated between different industries.

Just because people use the custom extension feature a lot with embedded, does not imply that the same thing happens for desktop/server. The constrains are different, the market is different, the industry is different. So far we have seen all linux distribution build on the same profile.

> Economics. RISC-V has actively courted embedded, which makes sense as a niche.

Actually wrong. The first profile that was standardized was the one for full linux.

Embedded simply got more interest because more people could get it to market faster, and many universities work on embedded.

This is open source, people are just gone use it for what they want, and embedded had the most need and the lowest barrier to entry.

> Openness doesn’t tickle down. The openness of an ISA doesn’t have much impact on the implementation. A design with restricted signing keys is completely acceptable under their licensing

The point of RISC-V to make it POSSIBLE to create an open chip and use it commercially.

People for many reasons wanted to use open implementations, and RISC-V makes this possible.

And thanks to this philosophy there are actually where nice open chips and open chips that have commercial appeal.

To say well not everything is open therefore its bad, is just such a wrongheaded attitudes, its unbelievable.

> Design flaws. RISC-V seems like it hasn’t learned anything from CPUs designed after 1991.

If you actually read the spec, the literally have design consideration for every instruction with all the learning from the past and why they did them. Simply because you don't agree with all their conclusions, doesn't mean they didn't learn anything.

And when drawing conclusions from only point out the issues with one side, without considering the others, you are just not doing serious analysis.