366 karma · joined May 22, 2018
If you highlight on the server:
pros: no javascript, can cache
cons: might be a way to inject scripts into everyone's browser, since the client has to trust the html from the server
--
If you write it on the client:
pros: server can't distribute injected scripts, server stores less things
cons: more javascript, every client has to do work
--
All software choices are weighing the pros and cons. Do the thing that lets you work quickly and safely.
While I am a Christian, I don't agree with 100% of this set of rules. For a small sample,
> Chastise the body.
> Recognize always that evil is your own doing, and to impute it to yourself.
> Daily in your prayers, with tears and sighs, confess your past sins to God, and amend them for the future.
> Obey in all things the commands of those whom God has placed in authority over you even though they (which God forbid) should act otherwise, mindful of the Lord's precept, "Do what they say, but not what they do."
That is not biblical (well, those could be in the Catholic bible, not 100% sure) at all, but that's fine. Now we all know where they stand, and what they find important.
1. Someone on the internet has a different opinion than you, therefore they are wrong.
2. Someone on the internet has a closed community (ie codebase that does not accept outside contributions), therefore they are terrible leaders.
--
Don't conflate a project's opinions with their technology. Consider this; do you think the team wrote this code of ethics to offend people, or to demonstrate their opinions on certain topics? I do honestly believe that the sqlite team believes these things, and is that wrong that they choose to believe this?
> No need to first install the command on the other machine.
and
> It must be installed on your own machine and any machines that you'll be using to run commands. On those other machines you must make sure to install it globally, such that it can be started with a command like ssh user@host outrun.
Not sure if the readme is just out of date, or if I'm misunderstanding the initial statement about the _other machine_.
And I think if someone is to build this containerized system for testing, it shouldn't necessarily be some app developer like me, it should be someone like the chromium or firefox team that know exactly how the browsers expect to communicate
I cut out audio and video from my features, and for the most part, things are working just fine.
The ICE/Turn server stuff is also a mess. I ended up installing and hosting a coturn server on digital ocean, and it was a pain. Documentation wasn't great, stackoverflow/forum questions were typically old, and there didn't appear to be any obvious alternatives.
I also tried simple-peer by feross, which seemed to be fine, and most quirks remained as browser issues.
I ended up ditching webrtc and went with a server with websockets. With peer to peer, I'm stuck using a server somewhere, so I'd rather use a websocket server. Webrtc just introduced too many unknown variables. Is there a problem with an ICE/Turn server? Is there a LAN issue? Can browsers vendors properly do p2p to each other without a bunch of "if firefox, do this, if chrome, do this, if something else, panic"? The websocket server took 100% of these concerns out of the equation.
I'd love to be able to use webrtc confidently, but with the current tools for implementing and testing, I don't think I can say it is for myself.
So I think the TLDR is that webrtc peer to peer isn't really consumer-ready. The browser support seems a little hit and miss, testing through a LAN appears to be very flaky, and testing via node/some other framework is spotty at best.
1. Work in a place that you don't normally use to relax when you would get home from work. Maybe a spare bedroom, maybe the kitchen with a stool. 2. Start work on time, and keep your schedule as non-pandemic-y as possible. Don't sleep in until a minute before work, but get up and pretend to do your commute. Make sure you make your coffee early, too. 3. When your done work on the clock, STOP ANSWERING EMAILS/SLACK/WHATEVER IS WORK RELATED. Now you're home for real.
I've worked on and off remote in software, and has saved my sanity every single time. The biggest thing is people are afraid to say no, but in reality, if your boss asks you to do work after you're done your day, either ask for overtime or don't even answer it. It's not your responsibility to work when you're off the clock. If your work would force you to work after-hours even before the pandemic, then there are a few problems: the bosses don't understand the work you do, they don't respect your time, and/or you enable them by working beyond your hours.
For myself, I always install global-recommended packages as dev dependencies. It can be a little painful, but it also means there are no special install instructions, and it _just works_ (tm).
On the flip side, if you want easy configuration, then yes, vim/emacs/similar are not necessarily the right choices for you, but I don't think that means they are generally bad options.
In terms of other things, JSX has nothing to do with stateless components, it's just a way to simplify writing `React.createElement(yourElementOrTagName, { ...props }, [ ...children ]);`
And for debugging, the absolute best advice I can give is to build smaller components, and use something like storybook to demo/isolate behaviour and tinker with it.
In general, react is a perfectly fine choice, though. I don't think it's any more strange than angular/vue/hyperapp/etc., but it is certainly lower level, which can feel less intuitive.
Let me answer your question with your own quote:
> The thing is, everyone I speak to in the project hates it and not just because it’s new and they don’t like change.
Tech industry is all about change, and since there is so much change, we have to rely a lot of having good processes that can be applied to all sorts of changes. It does sound like your company dropped a bomb of a bunch of changes - they probably could have baby-stepped into code review before also switching to git. Too much change is hard for anyone. But I don't think your company's problem is git.
I used to be the guy that had a single branch project with pushes directly to master, live changes on production, some days had multiple deploys as we discovered bugs. While that was _easy_ from the perspective of "hey, I could just push code, and it was great", it was hard because all deploys were high-stakes, and could mean spending hours debugging and redeploying into the after hours of my work day (and this happened regularly).
Just to ask a question back to you, how many times did your company's simple SVN process backfire and cause more work for you?
At this point, I don't think it's necessary to split them up for making copies. That said, a lot of churches have integrated chapter/verse look ups as part of their service/sermons/bible studies, so it would be very difficult to remove them now.