This is very high praise for something that only provides safety at compile time and not runtime.
925 karma · joined April 10, 2013
This is very high praise for something that only provides safety at compile time and not runtime.
Edit: Should note that our decoder was developed in house and I have nothing to do with the project OP linked to.
My ideal git workflow is pretty simple:
1. `git switch -C new-branch` 2. Make changes, time passes 3. `git add .` 4. `git commit -m "Description of changes made"` 5. `git fetch && git rebase origin/main` 6. `git push` 7. Make pr to main
If main is out of date I rebase again to update.
This to me feels pretty light weight and is not a hinderence in any way on my day to day tasks.
What exactly makes `jj` better? Is there a specific usecase i'm not understanding?
Navigating to "Virtual Field Trips" takes you to http://satftp.soest.hawaii.edu/maps/butbar.map . At this page you're greeted with what I take is instructions to paint out a frameset?
```
rect index.html 0 0 79 49
rect navnew/navigator.html 80 0 159 49
rect virtual.field.trips.html 160 0 239 49
rect http://radlab.soest.hawaii.edu/satlab 240 0 319 49
rect feedback.html 320 0 399 49
```
It's obviously "shape src x y width height" (or swapped around).
I'm having issues finding a resource that explains what this is and why it seemingly worked in a browser in the 90's but not now - i.e. when it was deprecated and to what degree it was supported prior. Does anyone know more?
I'm coming from a 4k screen, so that does play into it, but i honestly just could not read the article without changing the text properties here.
Even only considering JVM languages you run in to way too many options for the question in itself to be worth your time as a serious discussion.
IMO - use whatever you and your team like best and that suits your needs. Java is great for hiring new devs and is arguably the most well established in an enterprise settings.
If you want an actual answer: Personal preference.
I personally appreciate articles like this being posted, as they don't _really_ feel political and both lefties and righties can agree that freedom of speech and journalism is important. Except the extremists of course, as I'm sure I will be made aware of in any replies to this comment.
Will it pay off? Probably not. But is 25% a big share? Yes.
I'd say that gamble in particular worked. Not so sure others will though, audio books feels like it will be a dud.
Translated:
This is what the employees of tesla does not have compared to if they had a collective agreement:
- A complete insurance package with Fora
- The comprehensive adjustment support found in the main agreement between the social partners
- Salaries are lower compared to the average in the motor industry agreement
- Without the collective agreement no yearly raises are guaranteed
- No possibility of part time retirement
- They also do not have reduced working hours
Original:
Detta har inte de anställda på Tesla jämfört med om de hade kollektivavtal
- Ett komplett paket med försäkringar hos Fora
- Det omfattande omställningsstöd som finns i huvudavtalet mellan arbetsmarknadens parter
- Lönerna ligger lägre än genomsnittet i Motorbranschavtalet
- Utan kollektivavtal garanteras inte årliga löneökningar
- De har inte möjlighet till deltidspension
- De har inte heller arbetstidsförkortning
As many others have pointed out, these agreements are fundamental to the swedish labor market. While it's not as common in tech, industries like car manufacturing are almost completely covered.
I agree with the author to an extent - kafka is overly complex for low traffic systems. It can however be a godsend in specific cases, but what those cases are can be hard to pinpoint.
Not sure if this solves the issue. I personally recommend using git, but keeping it simple by limiting the allowed operations.
- git switch - git checkout - git add - git commit - git pull - git push - git rebase - git reset
Note the absence of merge and and cherry pick. Most often when a junior has messed something up it seems to be because of merging in a weird order or cherry picking the wrong thing before merging or rebasing.
Either my juniors have stopped asking me for advice (totally possible) or this recommendation helps. As I find myself very seldom needing those commands I hope and believe it's the latter :)
That being said - teenage engineering is probably not looking to compete with Zoom. The branding is totally different. TE is looking for a premium market, while the first thing I was met with on zooms homepage was a button that said "New lower price!".
Teenage engineering continues doing something that I don't really understand - making me want to buy stuff that is really expensive that I have no need for. I won't buy these things, but every time I see them I do appreciate the craft.
TBH I think it might've been a mistake from mastodons side to allow media hosting. Running ffmpeg in the background to transcode video, the image optimization scripts and the hosting of it all gets a bit costly.
I might be wrong on this, I don't run an instance myself, but in my perspective cost cutting should be prio number 1 even if it means you have to cut back on some features. Removing toot edits should allow for a more aggressive caching strategy etc.
This should allow more people to start their own instances without being afraid of potentially hitting it big.
In Niemanns case people have joked about vibrating anal beads communicating in morse code as well as shoe inserts.