The documented one. It is hell to work with APIs where only the happy path is documented.
The documented one. It is hell to work with APIs where only the happy path is documented.
I’m currently looking at onedev.io for personal and startup use but since I haven’t had an opportunity to test it out yet I can’t vouch for it. It looks cool though and seems to have a good rep.
XcQ, link stays blue
Funny, the forced indentation is what I hate about Python. If you think a missing semicolon can be hard to catch, don’t ever think about a missing whitespace :p
The end
keyword really isn’t a big deal for me. I find it to be a good way to easily spot the end of a method. But if you wouldn’t like it I’d still find it a good compromise to avoid syntax issues due to whitespace.
I think you’ll like Ruby. It has mostly done away with braces and code blocks end with end
, e.g.
def create
unless admin redirect_to new_session_path and return
@product = Product.new product_params
if @product.save
flash[:success] = "New product has been created!"
redirect_to edit_product_path(@product) and return
else
flash[:error] = "Something went wrong!
render :new
end
end
This is working code that I simplified a bit from an old project of mine.
I didn’t find any posts that meet the criteria.
It could be OC or not. Who knows really.
Beep Boop, I’m not a bot.
Neither do .dk domains, but in order to determine use the courts will have to be involved. I haven’t heard about a lot of those cases, but I’d guess you can prove use against the person who wants to take the domain. If I have a domain called firstnamelastname.dk it’d be pretty easy to show that I got a mail address at contact@firstnamelastname.dk that’s in use.
I simply don’t get why domain squatting is legal. On my ccTLD it is absolutely illegal meaning you have to forfeit the domain if you don’t use it anymore.
Code should always by itself document the “how” of the code, otherwise the code most likely isn’t good enough. Something the code can never do is explain the “why” of the code, something that a lot of programmers skip. If you ever find yourself explaining the “how” in the comments, maybe run through the code once more and see if something can be simplified or variables can get more descriptive names.
For me, that’s what was originally meant with self-documenting code. A shame lazy programmers hijacked the term in order to avoid writing any documentation.
What’s the difference?
Cause none of my choices of ISP supports it…
There are some times when Qwant returns bad results where I’ll revert to Google. Just to find worse results…
Jokes aside, Qeant handles most queries well, even local stuff in my native language.
No Tubular is just NewPipe with Sponsorblock. The original devs didn’t want to add that, so a fork was created to add it.
Nextcloud won’t be able to recognise new files if you do it that way. A full scan will be needed before they’ll show up in the web app.
Obligatory fuck DST
Only lunatics buy drives over 10 TB.
Hey! No need to call us out like that.
I got one shipped to Denmark after brexit and IIRC they handled all the customs and everything.
Ninja edit: It looks like you’ll pay taxes and customs fees on top of it if you order directly, so it might be a good idea to hunt for a reseller: https://discourse.osmc.tv/t/european-orders/96161/2 - apparently I was lucky and happened to order when they were trialling IOSS
The closest I can think of is a Vero from osmc.tv but that’s breaking the 100 mark.
I’ve got the old Vero 4K model and it works like a dream in conjunction with my Jellyfin server (it’s essentially a Kodi box so you can save media on it locally too).
/ Guitar Solo