In other news today...



  • @Mason_Wheeler said in In other news today...:

    @BernieTheBernie What salary does his contract say he's entitled to? If what they paid him was the wrong amount, then they should be able to reclaim it. But if they screwed up on the contract, they should have done a better job writing it.

    Forints.
    And the state prosecutor and whoever are helping the company:
    :ralph:



  • @jinpa said in In other news today...:

    @Mason_Wheeler It also depends on what the laws there are. The U.S. uses the UCC, which basically specifies the defaults, and then you can put most anything in the contract. Hungary and Austria may have a different split between what can be overridden in a contract and what cannot be as well as different defaults.

    But I think it's doubtful that his employer is just out of luck unless it was as you say.

    In Sweden I think the law used to be that whatever ended up in your bank account was yours. Until a bank was either using customer accounts to shovel large amounts of money around or fat fingered an account and someone ended up with millions in their account, noticed and moved it. The law was changed and now you can't just grab whatever is in your account as yours if it's unreasonable to believe it's yours.
    On the other hand, I think it's still hard for an employer that pays you to much to get money back unless it's voluntary. I got a double payout once, and was nicely asked to pay it back, which I did.


  • Discourse touched me in a no-no place

    @Arantor said in In other news today...:

    @DogsB said in In other news today...:

    @Mason_Wheeler are they keying everything in the dom to everything else in the dom.

    Don’t answer. I’m not going to like where it goes.

    Remember that React and co specifically create a “shadow DOM” so they go out of their way to minimise changes to the “real DOM” for “performance”.

    That performance, is it interpretive dance or maybe some sort of spoken word thing?

    (It's probably because there's too many things hung off the DOM that all get busy doing unwanted things immediately on a change, or maybe that DOM implementations are usually infested with copy-induced slowness... both of which are solved problems when not dealing with shitty software but this is web browsers we're talking here.)



  • @dkf they can't stop reinventing 50 year old things poorly just for some silly notion of performance, or lord save us, correctness.


  • BINNED

    @dkf (total ass-pull since I have no idea about these things): or maybe it’s because every minor change in the DOM triggers a cascade of listener events and recomputations.


  • Discourse touched me in a no-no place

    @topspin That's exactly what I meant when I wrote "too many things hung off the DOM that all get busy doing unwanted things immediately on a change". The solution is to delay the sending of the events slightly so that all the document changes are complete before the rendering engine (a necessarily complex and expensive bit of code) has another go.

    The downside is that it makes doing animations a bit trickier.



  • @dkf said in In other news today...:

    it makes doing animations a bit trickier.

    Animations that, for the most part, are unnecessary and simply design wankery. I have no objections to making them a bit trickier, or even impossible.



  • Well, React's shadow DOM absolutely is about minimising redraws - less the event bubbling because destroying and creating nodes is mostly event free - but there is a lot of fluff around reflowing all the shit around it.

    As for animations, there are all new ways to do this, including having a JSON blob describing an animation that gets pulled through a player to make a suspiciously dynamic SVG.

    But if you take away toys like the canvas and SVGs, people will only pull the kinds of shit like we used to in the olden days, like the "DHTML Lemmings" clone that achieved the digging out of pixels by lemmings via 1x1 divs of correct colour carefully overlaid and positioned.



  • @Arantor said in In other news today...:

    1x1 divs

    ca3252d2-ba14-43df-9614-d6f74f2ecb1a-image.png



  • @HardwareGeek Just saying if you take away their toys, they'll find more 'creative' ways to implement their bullshit. Better to give them the less awful toys.

    Mind you I am still often of the school that https://motherfuckingwebsite.com/ and its fancier big brother https://thebestmotherfucking.website/ are mostly all you actually need and the rest of it is pure bollocks.



  • @Carnage said in In other news today...:

    On the other hand, I think it's still hard for an employer that pays you to much to get money back unless it's voluntary. I got a double payout once, and was nicely asked to pay it back, which I did.

    That would never happen in my country, because nobody would ever ask nicely.


  • BINNED

    @hungrier said in In other news today...:

    @Mason_Wheeler said in In other news today...:

    (Rendering two triangles requires 6 vertices with all their associated information, compared to only 4 for a single quad, just for starters, so add on another conservative estimate of a 50% performance penalty there.)

    You'd have to go out of your way to turn what can be a 4 vertex triangle strip (or maybe something even more optimized) into two separate triangles

    I don’t think WebGL supports strips.

    … did Windows secretly get ported to JavaScript? That would explain a fair few things.

    Edit: I might have thought wrong. :kneeling_warthog: :barrier: 🔎



  • @kazitor said in In other news today...:

    … did Windows secretly get ported to JavaScript? That would explain a fair few things.

    That is a language you can use to write Metro Modern UWP Windows App programs, so it's possible parts were.


  • Notification Spam Recipient

    :tinfoil-hat: they don't want us to know!



  • @Arantor said in In other news today...:

    a JSON blob describing an animation that gets pulled through a player to make a suspiciously dynamic SVG

    😨 😨 😨 😨 😨 😨 😨 😨 😨 😨
    What an abomination! How can I be sure that I will be able to disable that shit on my browser?
    (Or may I be fortunate by my old Firefox not being capable of doing that shit? 😌 )



  • @DogsB said in In other news today...:

    Git would have been a nonstarter if SSDs didn't take off.

    Git was perfectly snappy from the start when SSDs were just starting (and I didn't have an SSD in my home computer until two years ago anyway) in Linux. Windows somehow manages to totally suck at listing directories and reading metadata. Apparently something isn't getting fully cached.

    I had a big tree under git where status took around 30 seconds cold on both Linux and Windows (7) on spinning disks, but then it was almost immediate hot on Linux, but hot on Windows it still took around 5 seconds.

    @DogsB said in In other news today...:

    Browsers have to be the worst. They actually have gotten better but they're obviously not doing much QA because they break constantly, do odd things and like to eat ram. I still don't understand why six tabs needs a gig.

    Browsers do do QA and do care about performance. There are two problems:

    • The conflict between efficiency and security tends to be resolved in favor of security, by creating subprocesses for different tabs or different origins, but that means many internal structures get duplicated that would be shared if it was a single process.
    • The web page authors are trying to do more and more in JavaScript, but that wasn't designed for performance, and while there is a significant effort towards making it efficient, the web page bloat grows faster (Wirth's Law again). And browsers are shy of just applying arbitrary resource limits to the pages.

    @DogsB said in In other news today...:

    I have no idea what the devil Microsoft is up too but they need to stop it.

    Devil Microsoft does not have any idea what they are up to either. They have way too many teams, each doing things differently. Most have one thing common though, the :shipit: culture.



  • @BernieTheBernie said in In other news today...:

    @Arantor said in In other news today...:

    a JSON blob describing an animation that gets pulled through a player to make a suspiciously dynamic SVG

    😨 😨 😨 😨 😨 😨 😨 😨 😨 😨
    What an abomination! How can I be sure that I will be able to disable that shit on my browser?
    (Or may I be fortunate by my old Firefox not being capable of doing that shit? 😌 )

    Given that the player is straight JavaScript, and all the features used (namely SVG manipulation) are actually standard DOM changes, the answer is going to be a hearty, healthy fuck you and your browser.

    Though I would possibly suggest some wildcard blockage for https://unpkg.com/@lottiefiles/lottie-player@latest/dist/lottie-player.js

    You won’t stop the geniuses that bundle this shit into the monolithic JS bundle but folks who include the player from the CDN will usually use this URL.



  • @Arantor said in In other news today...:

    Just saying if you take away their toys, they'll find more 'creative' ways to implement their bullshit.

    My experience with global variables. Take them away, and the Kevins, Jims, & Co. will find alternatives:

    • Singleton
    • static class
    • environment variable


  • @da-Doctah said in In other news today...:

    @Carnage said in In other news today...:

    On the other hand, I think it's still hard for an employer that pays you to much to get money back unless it's voluntary. I got a double payout once, and was nicely asked to pay it back, which I did.

    That would never happen in my country, because nobody would ever ask nicely.

    Carnage 🔫 :phb:
    And I used to think that that is deemed "nice behavior" in the US.
    :trollface:



  • @Arantor said in In other news today...:

    @DogsB said in In other news today...:

    @Mason_Wheeler are they keying everything in the dom to everything else in the dom.

    Don’t answer. I’m not going to like where it goes.

    Remember that React and co specifically create a “shadow DOM” so they go out of their way to minimise changes to the “real DOM” for “performance”.

    And the other frameworks specifically forgo creation of a “shadow DOM” for sake of performance.

    The reason for “shadow DOM” is to make things simpler and more robust. Instead of tracking what needs to change when, React simply recalculates the shadow DOM and then compares it to the real one and updates only what changed. Which is less efficient than tracking what needs to change when, as some other frameworks do, but it also minimizes the risk something won't update when it should.


  • 🚽 Regular

    @DogsB said in In other news today...:

    :tinfoil-hat: they don't want us to know!

    Old news.


  • Notification Spam Recipient

    @Bulb said in In other news today...:

    Git was perfectly snappy from the start when SSDs were just starting (and I didn't have an SSD in my home computer until two years ago anyway) in Linux. Windows somehow manages to totally suck at listing directories and reading metadata. Apparently something isn't getting fully cached.

    I had a big tree under git where status took around 30 seconds cold on both Linux and Windows (7) on spinning disks, but then it was almost immediate hot on Linux, but hot on Windows it still took around 5 seconds.

    I'm pretty sure that's just brillance of git developers, not Windows. For me git got fast and snappy when I switched to GitKraken, which uses libgit2.
    Experiences with SourceTree, GitExtensions, console client, etc were pretty horrible - 'original' git being the common denominator.


  • BINNED

    @MrL :why_not_both:

    Supposedly, original git was just a bunch of shell scripts in a trench coat pretending to be a VCS.
    Also supposedly, Windows is/was (?) slower at launching countless processes. (Although I still think the Unix fork model and it’s justification of “but it only took 30 lines to implement, 50 years ago” are retarded.)



  • @kazitor said in In other news today...:

    I don’t think WebGL supports strips.

    Briefly googled, and the first hit says it does (gl.TRIANGLE_STRIP; they also have fans gl.TRIANGLE_FAN).

    I think the problem is more that if you're drawing enough quads/rectangles for it to matter in the first place, you'll end up pushing against the limit of draw calls more than against any limits in rendering. Batching draw calls is important, but triangle strips make that a bit awkward. I'd first go for indexed meshes. You can then combine with triangle strips if you have primitive restart. You can also cobble something together with e.g. gl_VertexID + pulling out of buffers (although if you want to utilize the post transform cache, you'll still want indexing; not that it matters, because the vertex shader is likely to be very cheap in these cases).



  • @MrL said in In other news today...:

    I'm pretty sure that's just brillance of git developers, not Windows. For me git got fast and snappy when I switched to GitKraken, which uses libgit2.
    Experiences with SourceTree, GitExtensions, console client, etc were pretty horrible - 'original' git being the common denominator.

    Well, the problem is really in the interaction between the windows API and the cygwin/msys2 library exposing a posix-compatible interface on top of it. The mismatch between the interfaces mean that library ends up doing a bunch of extra calls. Ones that should be fast, but are not due to the way the interface is designed.

    I suppose libgit2 reimplemented a WinAPI-native version of the functions most affected by this.

    @topspin said in In other news today...:

    Supposedly, original git was just a bunch of shell scripts in a trench coat pretending to be a VCS.

    Most version control systems started that way. But that version never worked on Windows at all. It was mostly rewritten in C at the point I'm talking about.

    Also supposedly, Windows is/was (?) slower at launching countless processes. (Although I still think the Unix fork model and it’s justification of “but it only took 30 lines to implement, 50 years ago” are retarded.)

    It is, but it is not relevant here, because at that point git wasn't launching any additional processes for status.



  • @Bulb said in In other news today...:

    @Arantor said in In other news today...:

    @DogsB said in In other news today...:

    @Mason_Wheeler are they keying everything in the dom to everything else in the dom.

    Don’t answer. I’m not going to like where it goes.

    Remember that React and co specifically create a “shadow DOM” so they go out of their way to minimise changes to the “real DOM” for “performance”.

    And the other frameworks specifically forgo creation of a “shadow DOM” for sake of performance.

    The reason for “shadow DOM” is to make things simpler and more robust. Instead of tracking what needs to change when, React simply recalculates the shadow DOM and then compares it to the real one and updates only what changed. Which is less efficient than tracking what needs to change when, as some other frameworks do, but it also minimizes the risk something won't update when it should.

    Huh, TIL, I’d always understood it was for performance rather than encapsulation but honestly I try to steer clear of all of it partly because I hate React and partly because I try to keep my UI simple enough to not need that level of stuff where it’d matter.



  • @Arantor It is performance in the sense it is a massive improvement over the first version that just kept rebuilding the real DOM on each change.

    But the rebuilding of DOM came about from the desire not to deal with dependencies too much. Which does make the application simpler to write and more robust. But not as efficient as the frameworks that do deal with detailed dependencies between individual values and template expressions.


  • Discourse touched me in a no-no place

    @Bulb said in In other news today...:

    I had a big tree under git where status took around 30 seconds cold on both Linux and Windows (7) on spinning disks, but then it was almost immediate hot on Linux, but hot on Windows it still took around 5 seconds.

    That's probably related to the exact way in which listings and obtaining file metadata are done. And AV products may well interfere as well.



  • @dkf It is. But anything that uses a posix compatibility layer, any posix compatibility layer, will always be hit. No antivirus or other crap need to be involved. In fact, it shouldn't be involved anyway, because the content is not being read, only the metadata.



  • The company said full-time employees can book a room at an on-campus hotel in Mountain View for $99 a night [...] the company will not reimburse their stays, [...]

    “Just imagine no commute to the office in the morning and instead, you could have an extra hour of sleep and less friction,” the description reads. “Next, you could walk out of your room and quickly grab a delicious breakfast or get a workout in before work starts.”

    I don't get it. If I'm working from home, I also don't have a commute, get to stay that extra [half] hour in bed. Granted, the delicious breakfast is up to me, but on the other hand, it's a lot less than 99 US€.


  • BINNED

    @cvi they’re retarded. That’s what you’re not getting.

    Filed under: Did Silly Valley reinvent the bus again?



  • @cvi Plus it only works for those young single people. (Oh yeah, Google...) Those people probably look at you :sideways_owl: if you said "work life balance".



  • @cvi said in In other news today...:

    The company said full-time employees can book a room at an on-campus hotel in Mountain View for $99 a night

    I'd say they need to pay me more than $99 per night for me to do that. The going rate for overnight stays is around $600.


  • I survived the hour long Uno hand

    @Carnage said in In other news today...:

    @cvi said in In other news today...:

    The company said full-time employees can book a room at an on-campus hotel in Mountain View for $99 a night

    I'd say they need to pay me more than $99 per night for me to do that. The going rate for overnight stays is around $600.

    You misread. They're not paying the Googler for that. They're giving the Googler access to a discounted rate that the Googler can pay themselves.



  • @izzion said in In other news today...:

    @Carnage said in In other news today...:

    @cvi said in In other news today...:

    The company said full-time employees can book a room at an on-campus hotel in Mountain View for $99 a night

    I'd say they need to pay me more than $99 per night for me to do that. The going rate for overnight stays is around $600.

    You misread. They're not paying the Googler for that. They're giving the Googler access to a discounted rate that the Googler can pay themselves.

    You misunderstood my intent.


  • ♿ (Parody)


  • BINNED

    @Carnage said in In other news today...:

    @izzion said in In other news today...:

    @Carnage said in In other news today...:

    @cvi said in In other news today...:

    The company said full-time employees can book a room at an on-campus hotel in Mountain View for $99 a night

    I'd say they need to pay me more than $99 per night for me to do that. The going rate for overnight stays is around $600.

    You misread. They're not paying the Googler for that. They're giving the Googler access to a discounted rate that the Googler can pay themselves.

    You misunderstood my intent.

    Well I misinterpreted both of you! :topper:


  • Notification Spam Recipient

    @cvi said in In other news today...:

    for $99 a night

    Is my hourly $175? 🤔





  • whistles Jurassic Park theme



  • @DogsB said in In other news today...:

    Then you have weird things like slack and teams. Why do they take two minutes to load. Why are they so slow and unresponsive? Why do they spike to 100% every now and then when I'm not doing anything with them? You could blame the webby thing underneath but vs code is actually pretty solid and probably the leading example of that tech working well.

    people didn't write ides on interpreted programming languages in the 90s



  • @Arantor said in In other news today...:

    whistles Jurassic Park theme

    X-Files seems more fitting.



  • @Carnage true, you have that exact plot going awry in the X-Files but that doesn’t convey the sense of “science is gonna do something that they’ll be too busy thinking if they could rather than if they should, and it’s going to go very very wrong” that Jurassic Park does.


  • ♿ (Parody)



  • @boomzilla the drawings of the penises is the old and honourable tradition, no?



  • @boomzilla

    In Roman era, dicks were drawn onto the road indicating the direction towards a brothel.


  • ♿ (Parody)


  • Discourse touched me in a no-no place



  • @loopback0 In other news, a bunch of Zoom employees are looking for housing further away from the office.


  • Notification Spam Recipient

    @TimeBandit said in In other news today...:

    @loopback0 In other news, a bunch of Zoom employees are looking for housing further away from the office.

    "my home office is in another country. I'm shift 8 which looks suspiciously like I'm over here, but trust me bro!"


Log in to reply