I see it as taking the copyright holder's control over their material, not taking the material itself.
In other words, if someone publishes your works for free that you would otherwise charge for access, they haven't taken your work, they've taken your control over the access to it.
If you're using Terraform, why are you having problems with the interconnectedness? That's exactly the benefit of Terraform. Parameterizing all the configuration dependencies is its brilliance. Nothing I've come across is as simple and easy to use and understand while still being able to fully managing an entire infrastructure.
I wouldn't say we were having problems using Terraform for interconnectedness. The complexity of services used at this point warrants a person who can evaluate the architecture we've created. Can we optimise for cost, did we make the right MZ decisions, etc.
Terraform was what made AWS possible for us. I would not have used the GUI.
> I think would try to use its panic/recover mechanism as much as possible
And that's exactly the reason you should avoid Go. Every error is not exceptional. Most errors are not exception. Hence, most errors should not panic.
> to avoid the tedious multi-level error handling.
It only looks tedious to the uninitiated based on code snippets you've probably seen. Or if you're stuck in an imperative paradigm, i can imagine Go will feel tedious. But since Go has first class functions, it's quite easy to write high-order functions that work better than try/catch and make error handling flow quite nicely. It also provides better error handling than cumbersome, coarse-grained, and verbose try-catch clauses where the catch clause is not directly related to the call that produced the exception (which probably isn't really an exceptional case but rather just a simple error.)
Yea, Python can do the same but because Exceptions exist, everyone considers simple errors to be exceptional. Go allows errors to just be errors and error handling becomes related directly to the call that caused the error.
Users of languages that have excellent support for first-class functions and exception handling will probably not agree with you, sorry.
Lower-level code often doesn't "know" how to handle a situation when it is not able to complete its job. The executive decision about how to proceed is somewhere higher up.
Returning an error code that has to be propagated through several levels to the appropriate place is blub programming that belongs to the 1960's.
Higher order functions are useful for error handling, but only when coupled with a dynamic control transfer. The low-level routine invokes a callback, which is some closure belonging to a higher level. For this architecture to be useful to its full potential, that closure must be able to make a jump (for example, a jump to the surrounding code in the function where that closure was created, to effectively abort all the frames between that function and the low level where the error occurred).
I was _only_ pointing out, through _one_ simple example, the flaw in your conclusion of Go errors being tedious. I was not discussing other languages nor how to incorporate extensive and fluid error handling in Go to be as capable as any in other language. And since you've raised several points that weren't pertinent, it seems you simply want to disagree with me, so i'll end my side of this discussion. Have fun.
If the authors are opposing advertising, why are they advertising their opinions here? These naive opinions are more intrusive to me than many targeted advertisements. To be clear, i'm not opposed to ad blockers. I'm also not opposed to some advertising. I am averse to hypocrisy.
Your argument falls apart when you consider HN is explicitly a place to advertise either ideas or products. And you can show your disdain via the downvote button or you can offer criticism in the form of comments. This is a platform for advertising, whether there's money to be gained or not.
Just silly! Pioneers are more important than bringing the pioneering to the masses. We don't pioneer for perfection, we pioneer for discovery. Completely different purposes but without discovery, there is nothing to perfect.
Additionally, light on dark is horrible for readability. That theme is great for imagery but it's doesn't provide valuable contrast for clearly rendering fonts. Programming docs are typically mostly text so should provide the best colors that support readability.
>Additionally, light on dark is horrible for readability.
I have a hard time understanding this. Staring at a bright background hurt my eyes after a while. White text on a black background feels much more comfortable to read. What am I missing?
Context. If I'm in a bright room (office), and the last page I visited was black on white (the default/norm on the web), and the page I view after this one will be black on white (most likely), then viewing this one in the middle in white on black is jarring, annoying, inconvenient, distracting, hard to read (because my eyes have to adjust) etc.
If one is in a dark room, and has a custom stylesheet to display all pages in white on black, or if the web were predominantly white on black, then sure it's OK.
I agree with this. We've gotten a bit of flack on blog.darknedgy.net for this, and we've been putting off making a light-background alternative theme. I'll get around to it eventually because people want it, but I prefer the darker background with lighter text. It feels easier on the eyes for me, personally.
And really, folks who have complained have been the minority anyway. For us anyway.
You should read the link I posted in the sibling to your comment[1].
You may personally feel that light-on-dark is better, but your visually-impaired users will disagree. This includes a huge number of older users, as eyes deteriorate significantly with age (even among people in their 40s and 50s).
Also, you have no idea whether the complainers are in the minority or not. The people it bothered probably didn't stay long enough to figure out how to complain. Do you get compliments from people who say that they're glad you use light-on-dark?
I am not sure I agree. Do you know what I do when I have trouble reading the text in a page. I increase font size. It is only a flick of your finger (ctrl+mouse wheel). So the point is if you have a big enough font size, white on black can be just fine.
Also, should we assume that the people have their vision uncorrected?
I think that black on white is just a fad, perpetuated by following conventions. Like glossy screens.
I did find that it doesn't meet my needs exactly, however. I favorited a number of inbound numbers such as Pingdom and co-workers to allow for alerts to come through but it doesn't apply to SMS messaging. They simply get muted, even if the number is in your favorites. I had to turn off "Do Not Disturb" simply because overrides wouldn't be triggered by SMS messages.
I believe it should apply to both SMS and phone for the overrides.
In other words, if someone publishes your works for free that you would otherwise charge for access, they haven't taken your work, they've taken your control over the access to it.