[-] Buttons@programming.dev 2 points 8 hours ago

I wouldn't consider Julia statically-typed; am I wrong?

[-] Buttons@programming.dev 3 points 9 hours ago

The question mine as well be "what is your favorite compiled language?". There is a lot of overlap between the possible answers.

[-] Buttons@programming.dev 4 points 2 days ago

I hear you. It's no good to just cede ownership of a word and allow others to define it however suits them. But... it's Twitter, getting into a good faith philosophical discussion about the definitions of words ain't going to happen, so in many cases it's better to just not bring up the controversial words at all. Guess there's pros and cons to each.

[-] Buttons@programming.dev 2 points 2 days ago

I agree. That's why I suggest (or more like implied) that when we know we have different definitions of a word, we avoid using that word. It's a good thing to at least try if two people really care about understanding.

[-] Buttons@programming.dev 6 points 2 days ago

"Woke" is a problem because people have different definitions, and no matter what Webster or any other authority says the definition is, people will continue to have differing definitions.

How can we reach understanding when we don't even agree on the definition of words?

This is way to nuanced to deal with on fucking Twitter. If you use the word "woke" on Twitter, expect a lot of misunderstanding, talking past each other, and bad faith arguments to follow.

[-] Buttons@programming.dev 9 points 2 days ago

I did not suggest banning any words.

To understand why I'm opposed to the word "woke", you must first acknowledge this fact:

Sometimes people have different definitions of the same word.

If you're willing to accept that, then it logically follows that using a word that people have different definitions of will cause more confusion than understanding. If our goal in speaking is to convey understanding, then that is best accomplished by avoiding words where people have conflicting definitions.

We've all learned that there are facts and opinions, but there is a third category: definitions.

If you watch for it, you will see that many disagreements boil down to nothing more than disagreeing about the definition of a single word. If we temporarily avoid using that word, suddenly we find ourselves in agreement, or at least having a better understanding of each other.

[-] Buttons@programming.dev 55 points 3 days ago* (last edited 3 days ago)

Finally a place I can share my cold takes. (I'm not on Twitter, I won't discuss this on Reddit either.)

  1. The community manager had a meltdown and blocking everyone was a power trip and was wrong.

  2. Godot's tweet was wrong, because it used the word "woke" which immediately drives any conversation into the gutter. Doesn't matter if you're on the right or left, as soon as you say the word "woke" you have ruined the conversation.

  3. It is good that Godot explicitly supports LGBT+ people. They should be welcome. The community CoC should make this explicit, and it does. A tweet to reaffirm this is fine, a cringe joke born from the dredges of Twitter is less fine.

  4. Godot's "revenge forks" are amusing and will not go anywhere. Someone might collect some donations before grifting into the night though.

  5. None of this has any effect on Godot's technical suitability for creating a game.

[-] Buttons@programming.dev 5 points 4 days ago* (last edited 4 days ago)

How would you force someone to take time off?

If I was their boss I would say something like "you're job is to stay home and do anything besides work for the next week, you will still be paid for this time". Easy.

As for the on-call stuff. Yes, that's the point. It should be unsustainable for a company to continually rely on their daytime programmers for frequent on-call alert handling.

If off-hours issues happen often, the company can hire an additional team to handle off-hours issues. If off-hours issues are rare, then you can depend on your daytime programmers to handle the rare off-hours issue, and know that they will be fairly compensated for being woken up in the middle of the night.

I've been at too many companies where an off-hours alert wakes up a developer in the middle of the night and the next day the consensus is "that's not good, but we'll have to fix the underlying issue after we finish implementing the new UI the design team is excited about". It's not right for a developer to get woken up in the middle of the night, and then the company puts fixing that on the backburner.

I'll say it again. It's about aligning incentives. When things that are painful for the worker are also painful for the company, that is alignment. Unfortunately, most companies have the opposite of alignment, if a developer gets woken in the middle of the night the end result for the company is that they got some additional free labor, that's pain for the worker, reward for the company; that's wrong.

[-] Buttons@programming.dev 36 points 4 days ago* (last edited 4 days ago)

When I think of a tech worker union my thoughts first go to standardizing everyone's pay and limiting what I can earn myself. I've probably fallen to anti-union propaganda.

A tech worker union that says nothing about pay could still do so much.

A union could ensure that the company's incentives are aligned with worker's incentives around things like on-call.

I'd love a union that forced a company to give all on-call workers compensation. Something like:

  1. If you're woken up in the middle of the night, you automatically get 8 hours comp time (time off), plus 2x the time you spend on-call during off hours.
  2. Accrued comp time over 20 hours must be payed at 10x normal pay if the employee leaves the company for any reason. The idea here isn't for employees to accrue comp time, but to give the company a strong incentive to ensure employees use their comp time.

Basically, if a company is having lots of on-call alerts, or the company is preventing employees from using their comp time, you want this to be directly painful to the company. Incentives should be aligned, what is painful for the worker should be painful for the company.

Or, regarding "unlimited PTO". I'd love to see a union force companies to:

  1. "Unlimited PTO" policies are fine, but they must have a guaranteed minimum amount of PTO specified in writing. So none of this "yeah, we heave 'unlimited PTO'; oh, we're really busy this quarter, so can you wait to take PTO until next quarter?".

Tech workers have it good compared to a lot of workers, but there are still plenty of abuses a union could help with, even if the union never even mentions pay.

[-] Buttons@programming.dev 294 points 1 week ago* (last edited 1 week ago)

Ads will always be detectable because you cannot speed up or skip an ad like you can the rest of the video.

If they do make it so you can speed up or skip the ad sections of a video, mission accomplished.

If all else fails, I'd enjoy a plugin that just blanks the video and mutes the sound whenever an ad is playing. I'll enjoy the few seconds of quiet, and hopefully I can use that time to break out of the mentally unhealthy doom spiral that is the typical YouTube experience.

[-] Buttons@programming.dev 179 points 2 weeks ago* (last edited 2 weeks ago)

Patents and video games huh? We can't ignore what John Carmack had to say about this:

The idea that I can be presented with a problem, set out to logically solve it with the tools at hand, and wind up with a program that could not be legally used because someone else followed the same logical steps some years ago and filed for a patent on it is horrifying.

--John Carmack

52
submitted 3 months ago by Buttons@programming.dev to c/linux@lemmy.ml

Git repos have lots of write protected files in the .git directory, sometimes hundreds, and the default rm my_project_managed_by_git will prompt before deleting each write protected file. So, to actually delete my project I have to do rm -rf my_project_managed_by_git.

Using rm -rf scares me. Is there a reasonable way to delete git repos without it?

[-] Buttons@programming.dev 119 points 4 months ago

You can tell how important working from the office is by the fact that they can't tell whether or not people are working from the office.

Maybe people need to start talking about unionizing while in the office.

17
389
submitted 7 months ago by Buttons@programming.dev to c/memes@lemmy.ml
60
Can anyone relate? (programming.dev)
1
submitted 1 year ago* (last edited 1 year ago) by Buttons@programming.dev to c/godot@programming.dev

I like most things I see about Godot, and I'm going to try making some games with it.

Whenever I imagine programming a game though, I imagine the game logic and simulation being separate from the display. For instance, if I was to make a game like FTL, I would plan to simulate all the ship interactions and the movement of the characters purely in code, and then write a separate module to render that simulation. The simulation could be rendered with graphics, or with text, or whatever (of course, a text render wouldn't be human friendly, but could act as a dedicated server for some games, or I could use it for machine learning, etc).

I'm not an expert at Godot, but it seems this mindset is not going to fit well into Godot. Is this correct? It seems like the same object that is responsible for tracking the players health is going to also be responsible for drawing that player on the screen and tracking their location on the screen, etc. Will my player class have to end up being a subclass of some complicated Godot class? (Also, I'm a fan of functional programming and don't always use a lot of classes if given the choice.)

What are your thoughts about this. Would you recommend another engine? No other engine seem to be in the same sweet spot that Godot is currently in.

4
submitted 1 year ago* (last edited 1 year ago) by Buttons@programming.dev to c/programming@programming.dev

My first experience with Lemmy was thinking that the UI was beautiful, and lemmy.ml (the first instance I looked at) was asking people not to join because they already had 1500 users and were struggling to scale.

1500 users just doesn't seem like much, it seems like the type of load you could handle with a Raspberry Pi in a dusty corner.

Are the Lemmy servers struggling to scale because of the federation process / protocols?

Maybe I underestimate how much compute goes into hosting user generated content? Users generate very little text, but uploading pictures takes more space. Users are generating millions of bytes of content and it's overloading computers that can handle billions of bytes with ease, what happened? Am I missing something here?

Or maybe the code is just inefficient?

Which brings me to the title's question: Does Lemmy benefit from using Rust? None of the problems I can imagine are related to code execution speed.

If the federation process and protocols are inefficient, then everything is being built on sand. Popular protocols are hard to change. How often does the HTTP protocol change? Never. The language used for the code doesn't matter in this case.

If the code is just inefficient, well, inefficient Rust is probably slower than efficient Python or JavaScript. Could the complexity of Rust have pushed the devs towards a simpler but less efficient solution that ends up being slower than garbage collected languages? I'm sure this has happened before, but I don't know anything about the Lemmy code.

Or, again, maybe I'm just underestimating the amount of compute required to support 1500 users sharing a little bit of text and a few images?

1
0
view more: next ›

Buttons

joined 1 year ago