• 0 Posts
  • 28 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle
  • dgmib@lemmy.worldtoMemes@lemmy.mlI hate the rich
    link
    fedilink
    arrow-up
    1
    ·
    1 month ago

    It depends on the jurisdiction, but in most cases if you have a salaried position with say 3 weeks of PTO but you only take 2 weeks of it. The employer is usually required to pay you over and above your salary for working during your “vacation time”.

    If there’s an unlimited PTO policy, they don’t have an obligation to pay you extra for working during vacation time.


  • dgmib@lemmy.worldtoMemes@lemmy.mlI hate the rich
    link
    fedilink
    arrow-up
    3
    ·
    1 month ago

    It’s a lie.

    By making it “unlimited” they don’t need to pay you out of you don’t use all of PTO days.

    If you use it more than they think you’ve earned you get terminated.

    Employees end up afraid of taking their PTO days and typically end up taking even less time off than if they knew there was a expectation of 3 weeks or whatever.




  • Money isn’t the limiting factor though.

    There’s plenty of money waiting to be spent on green electricity projects that’s bottlenecked by grid connections, permitting, panel and turbine manufacturing, rare element supply chains and host of other factors slowing down how quickly we can build new renewable capacity.

    Also the typical LCOE cost comparison approach doesn’t factor in the cost of grid connections, which is lower for a nuclear power plant than it is for an equivalent capacity of renewables. Nuclear is still more expensive on average, but the difference isn’t as clear cut and there a cases where nuclear might be cheaper in the long run.

    Everytime nuclear comes up on Reddit/Lemmy we always seem to argue whether nuclear or renewables is better choice like it’s a choice between the two. Both nuclear and renewables are slam dunk choices compared to fossil fuels on every metric if you factor in even an overly optimistic case analyisis of the financial impacts of climate change. (Nevermind giving considerations of the humanatarian impact.)

    80+% of our planet’s energy still comes from burning fossil fuels. Renewables have been smashing growth records year over year for a long time now and yet we haven’t even reached the point where we’re adding new renewables capacitiy faster than energy demand is increasing. We’re still setting new records annually for total fossil fuel consumed. Hell we haven’t even gotten to the point where we stopped building new Coal-fired power stations yet.

    The people who argue that “we don’t need nuclear, renewabes are cheaper and faster” you’re missing the reality of sheer quantity of energy needed. We can’t build enough new renewables fast enough to save us regardless of how much money is invested. There aren’t enough sources of the raw materials needed to make that happen quickly enough, we can’t connect them to the grid quickly enough, we cant build new factories for solar panels and wind turbines fast enough. Yes, we will undoubetly continure to accelerate our new renewables projects at a record setting paces each year but it’s not enough, it’s not even close. Even our most optimistic , accelerated projections don’t put us anywhere close to displacing fossil fuel consumption in the next 10-20 years.

    We need to stop arguing over which is better. We need to do it all.


  • Not sure where you’re getting 250kwh/m2/year from. If it was one contiguous solid panel maybe you could achieve that and then you’d be correct it would be about 560,000 km2. Or roughly the size of France.

    But you need to leave space between the panels in a solar farm for them to be at the optimal angle without casting shadows on each other. Real world solar farms have much lower density than that.

    The density can vary significantly, our hypothetical solar island could be anywhere from the 6th to the 50th largest country but regardless we’re still talking about something in the area of a trillion individual solar panels.

    Assuming money isn’t the limiting factor (which it isn’t in most countries) we don’t have anywhere close to the ability to manufacture and deploy that many panels by 2030 or 2035.

    Assuming we maintain exponential growth of both wind and solar (doubtful) we’re still a least two decades away from eliminating fossil fuel electricity generation never mind meeting the 2-3x generation capacity needed to transition transportation and other consumers of fossil fuels over to electricity.

    Renewables growth has shattered estimates before, you never know, but the transition is not happening any where near as fast as people seem to think.



  • Sandford Fleming (the guy who invented time zones) actually made it easier.

    Before timezones, every town had their own clock that defined the time for their town and was loosely set such that “noon is when the sun is at its highest point in the sky.” Which couldn’t be measured all that accurately.

    If it wasn’t for Fleming, we’d be dealing with every city or town having a separate time zone.



  • I question the methodology here. The same site lists Linux desktop share at 2% in my country specifically. It feels like if it was that high you’d see it on people’s laptops more in coffee shops and what not… but I’ve yet to see a single other person using Linux on the desktop.

    I know most of that 4% is in India… but still feels like it should be more ubiquitous if the number is that high.



  • It’s called home realm discovery. It’s common in business apps though it’s usually used with email & password logins not username & password logins.

    It’s done that way to support federated logins. Larger companies will often used a single sign on solution like Okta or Azure AD. Once the user’s email address is entered it checks the domain against a list of sign on providers for each domain and redirects the user to their company’s federated login if it finds it there instead of prompting for a password.

    This has several benefits:

    1. The user doesn’t have mutiple passwords to remember for different apps. Which is know to result in users either reusing passwords or writing down passwords somewhere.

    2. When an employee quits or is terminated the company only needs to disable their account in their company directory and not go into potential dozens of separate web apps to disable accounts.

    3. The software vendor never receives the password, if the vendor’s system is compromised they don’t even have password hashes to leak. (Let alone plain text or reversibly encrypted passwords)

    Websites that work that way are (usually) doing it right. If that doesn’t work with your password manager, you should (probably) blame the password manager not the website.


  • Reddit never expected the new api pricing to be a fountain or money. This was never about LLMs or the lack of ad revenue.

    If it was just about LLMs they could have made one price for api users that were primarily harvesting data and a different price for api users that contributed significant content or moderation. Which would make good business sense to do so as content contributors are what bring the eyeballs (and therefore the value) to the platform.

    It wasn’t about ad revenue either, by all estimates the revenue from a third-party app user would have been many times more than the opportunity cost from the ad revenue they were missing out on from 3rd party app users. If they wanted to profit from the api pricing, they only needed to give the community more time to transition business models. They didn’t even need to give everyone more time, just a dozen or so major third party apps.

    This was always about killing off the third party apps. The ones they let survive had low user counts to begin with and went even lower.

    I don’t know their real motivations here but so far there’s only two possibilities that i can think of.

    A) Reddit’s leadership and board of directors are beyond incompetent

    B) They collect significantly more data from the first party app than they were able to from the third party apps, and they’re selling that data for a significant sum of money beyond just their own ad ecosystem.




  • I will absolutely give you that transitioning an established mature product to the subscription model is usually a terrible idea. Plenty of examples of that going horribly wrong.

    As for subscriptions being a “blatant money grab” that definitely happens sometimes… notably when there’s a mature product with a dominating market share. The company already captured most of the market share, so they can’t get much more revenue from new customers, existing customers are satisfied with the version they have so they’re not buying any updates. Sales go down and someone comes along say just make it a subscription and keep milking the cash cow forever…. Yep, I admit it, that totally happens. The enshitification ensues.

    But none of that’s the fault of the subscription model per se.

    The same subscription model that becomes the incumbent’s downfall, is what creates a market opportunity for a new competitor.

    A new competitor can coming in with a new product that was built with a subscription model from the start. The competitors product is cheap to try for a month, cheap to switch to with no big upfront costs. The newcomers can generally react much faster to customers needs than the incumbent. (Not because of the model, they can because they’re smaller)

    Established software companies doing blatant money grabs happen all the time. Hell most of us are here using Lemmy because Spez attempted a blatant money grab on Reddit. Had nothing to do with the model.

    Subscription model gets a lot of hate because greedy companies tried to use it as a blatant money grab exactly as you described. But it doesn’t have to be that way.

    Subscription models make it easier for newcomers entering a space, which is good for consumers. It’s more compatible with agile development methodologies because you don’t need wait until you’ve bundled enough features together to market it as a new version worth upgrading to. It’s in your best interest to ship new features immediately as they’re developed.

    It’s totally fair of you don’t like the model.

    But the model itself isn’t the problem.

    Shitty companies being greedy will always happen.



  • Wow… lots of people in here bashing the subscription model, but let me point out it’s maybe not as bad as you think…

    If you sell a product under a perpetual license model (I.e the one-time purchase model). Once you’ve sold the product, the manufacturer has almost no incentive to offering any support or updates to the product. At best it’s a marketing ploy, you offer support only to get word of mouth advertising of your product which is generally a losing proposition.

    Since there’s little incentive to improve the experience for existing customers. Your main income comes from if you can increase your market share which generally means making products bloated often leading to a worse experience for everyone.

    If the customer wants support, you need to sell them a support contract. If they want updates you have to make a new version and hope the customer sees enough additional value to be worth upgrading. Either way we’re back to a subscription model with more steps, more risk, and less upside than market expansion so it takes a backseat.

    If you want to make a great product without some variation on a subscription. You need to invest heavily upfront in development (which most companies don’t have the capital to do, and investors generally won’t invest in unproven software)

    From a product perspective, you don’t know if you’ve hit the mark until people start using your product. The first versions of anything but the most trivial of products is usually terrible, because no matter how good you are, half to three quarters of the ideas you build are going to be crap and not going to be what the customers need.

    Perpetual licensing works for a small single purpose application with no expectation of support or updates.

    It works for applications with broad market needs like office software.

    For most niche applications, subscription models offer a better experience for both the customer and the manufacturer.

    The customer isn’t facing a large transition cost to switch to a competitor’s product like they would if they had to buy a perpetual license of it, so you have a lot more incentive to support and improve your product. You also don’t see significant revenue if the customer that drops your service a couple months in… even more reason to focus on improving the product for existing customers.

    People ought hate the idea of paying small reoccurring fees for software instead of a few big upfront costs. But from a business model perspective, businesses are way more incentivized to focus on making their products better for you under that model.


  • dgmib@lemmy.worldtoMemes@lemmy.ml6÷2(1+2)
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    10 months ago

    I concur with everything you’ve written here.

    I concur that a left-to-right interpretation of consecutive explicit multiplication and division is wide spread and how most calculators and computers would interpret:

    a / b * c.

    But the sources you quote in your blog post and the style guides I’ve read, state that a fraction bar or parenthesis should be used to clarify if it should be interpreted as:

    (a / b) * c

    or

    a / (b * c)

    You make the argument in your post that:

    a / bc

    is ambiguous (which I agree with)

    but

    a / b * c

    is not ambiguous. Which is the part I disagree with, and I think the sources you quoted disagree with you as well. But I’m open to being wrong about that and am interested if you have sources that prove otherwise.

    If I’m understanding your response correctly, you believe that

    a / b * c

    is unambiguous, and always treated like

    (a / b) * c

    because of a wide spread convention of left-to-right interpretation (a convention that we both agree exists), not because you found a source that states that.

    Anyhow… I’m not out to convince you of anything and I appreciate you taking the time to explain your thinking to me.


  • dgmib@lemmy.worldtoMemes@lemmy.ml6÷2(1+2)
    link
    fedilink
    arrow-up
    1
    ·
    10 months ago

    I would be particularly interested if you found something in a mathematical style guide that recommended an expression like

    ( a / b ) * c

    Should be re-written as

    a / b * c

    Generally speaking, style guides advise rewriting equations for maximum clarity. Which usually includes a guideline of removing parentheses when their existence isn’t needed to clarify intent.

    I believe, and I’m particularly interested to see if you found evidence that my understanding is incorrect, that the LTR convention used by calculators and computer programming languages today exists because a deterministic interpretation is a requirement or the hardware, not because any such convention existed prior to that or has been officially codified one way or the other by any mathematics bodies.

    So like, forget division for a sec…

    In a mathematics paper, you usually wouldn’t write:

    (a + (b + c)) + d

    You’d write:

    a + b + c + d

    (Except perhaps if in your paper the parentheses made it easier to follow how you got to that equation.)

    Because in mathematics, it will never matter which order you do additions in, so you should drop the parentheses to improve clarity.

    On a computer or a calculator though you might get a different result for those two equations like if a+b overflows your accumulator and c is a negative number, or when these are floating points values with significantly different magnitudes.

    I believe english speaking engineers just adopted LTR as the convention for how to interpret it since they had to do something, and the english language is a LTR language. I don’t believe that convention exists outside of the context of computing.

    The Wolfram quote and ISO quote in particular that you have in your post imply that an inline division followed by an explicit multiplication is ambiguous as to if it should be interpreted as a compound fraction.

    If that’s correct, then it would be the inline division that makes it ambiguous, not the implicit multiplication that makes it ambiguous.

    If there’s some source from before computers, or outside of the context of computers forcing a decision. Then your assertion that it is the implicit multiplication causes the ambiguity is correct.

    I’m not trying to prove you’re wrong, I’m just genuinely curious which it is. And if you found evidence one way or the other.