zubi

Quote from page 13:

`After extensive troubleshooting, IT personnel figured out they had to change several settings on Internet Explorer so ALIS users could log into the system. This included lowering security settings, which DOT&E noted with commendable understatement was “an action that may not be compatible with required cybersecurity and network protection standards.”`

They use Internet Explorer?

Mi forte rekomandas ke vi legu Gerda Malaperis ĉe lernu.net. Fakte, mi trovis ĉiu materialo sur lernu.net tre utila. Kaj tiam vi povas provi legi rakontojn de Fratoj Grimm, denove sur lernu.net. Alie, vi povas vidi videojn de Evildea sur Jutubo kaj aŭskulti podkastojn ĉe kern.punkto.info. Ne forgesu aniĝi al Duolingo Esperanto Learners ĉe Fejsbuko, se vi havas konton tie. Bonŝanson :)

I successfully learned Esperanto, extensively studying solely on duolingo for 3 weeks, then jumping on to other material. It was one of best things that I did for myself. I particularly recommend Esperanto to HN readers as the language itself is "hackable".

Someone already mentioned about the co library. My personal experience is that it is excellent and massively simplifies async calls. The API resembles the async/await pattern: you use the keyword "yield" instead of "await". Async calls look as if they are sync. The code that includes heavy use of async methods such as in a database application greatly benefits from co in terms of code readability.

I don't think it can be considered syntactic sugar. For one, writing .then( .. => return ..) everywhere is too verbose and using co means that you are using a library to achieve something that the language should have first class support in the first place. Moreover, async/await will have different semantics than generators, the runtime will have native support and no generators will be involved. Calling these solutions "we already had it", IMHO, is like saying we didn't need functional programming features like .filter, .map etc, or newer features like Object.create, Object.assign etc we already had polyfills or other ways to a achieve their functionality. For that matter, even a simple "for loop" is redundant as you can use a while loop and use your own counter to achieve the same results. Async/await as a language construct feels so much better and fulfills a very common pattern than verbose solutions or solutions with different semantics using libraries.

I really like KDE and installed Neon a few weeks ago. However, I encountered bunch of issues, sudden chain-crashes of software, some settings not being saved, plasmoids and wallpapers not being downloaded and most notably the digital clock displaying incorrect time (tried everything to no avail). For some reason it didn't work properly on my laptop. I ended up installing Kubuntu.

I, as an author of such library, am a bit biased but still...

For one, you may get massive, massive developer productivity by eliminating loads of queries. In a lot of ORMs you do things like myObject.save() instead of generating a insert/update query for the particular state of myObject without taking into consideration which fields of the object is currently set. This reason alone enough for me to use them.

Second, bunch of additional functionality usually come out of the box with ORMs, such as JSON or arbitrary (de)serialization of columns, caching, logging etc which you would have to spend time on custom implementations of these otherwise.

Third, like you mentioned, some allow very easy change of database vendor.

Fourth, mental abstraction from the underlying data storage (you stay in your language's domain) which again contributes to the productivity.

Some other benefits include not seeing large SQL strings in your code which make it more difficult to read and maintain, security and ability to easily reason about what the code intends to do.

I don't want to sound arrogant (not my intention at all) but I believe those who don't understand or downright rejects the benefits of a decent ORM system are either the ones that never used one to see the productivity benefit or those who work on projects that need to squeeze the last bit of optimization. In a large enough project it is seriously pain and time consuming writing all those queries which could be elegantly avoided.

They are not "banning" in the sense of disallowing or prohibiting. They just slow it down to the point where it is no more usable. Media is only as good as they serve to the needs of the government.

As for the justification, nowadays they don't really justify anything, they just do, and it doesn't matter if it is unlawful or not. Especially after the coup attempt, there's this state of emergency situation which allows the government to bypass the parliament which pretty much translates to no justification for anything, capability is enough and it is not difficult to find stuff to use as pretext. Many of the government's recent actions are gross violations of constitution and several other laws, all possible due to the emergency status.

I clicked on it even before reading the article. Not only the chrome crashed, but also my notebook! I had to reboot the computer.

Why would I have to know about that?

I can hardly believe this is never discussed on HN, is it fake or what?

Well, mainly not, due to some of the target visitor groups using Win XP.

I am aware of them and yours is a valid point. I, however, was referring to relying on the infrastructure, expandability, customer support etc. Aside, a fair comparison in terms of security can only be made in the long run as it is natural to think that Linode has been around much longer and it is much bigger meaning it has a greater window of opportunities to be targeted by attacks.

I share exactly the same feelings and experience with the person who replied to your comment previously.

I have a server in each and I like them both. However;

- Linode support is second to none. DO is not bad either but much slower and less responsive. You feel the difference when you really need it.

- I had a CC payment issue with DO since the beginning. I mentioned it to the support twice but unsolved as of yet, using paypal.

- You can't assign multiple IPs to your instance in DO. I have 6 IPs in one of my Linodes for SSL reasons. This is more than enough to compensate the price diff, actually Linode is cheaper because of that.

- No built in, easy-to-use load balancer in DO.

- Networking feels much faster and stable on Linode, at all occasions.

- Small things like "no more Amsterdam based droplets due to IP restrictions" when you urgently need a server don't usually happen on Linode.

Things like these pile up in the long run and you can easily justify the price difference. If have a very serious/critical project I'd definitly chose Linode over DO.

Ditto. Sleep and reading hacker news.

Turkuaz.