nahiluhmot
nahiluhmot on Hacker News
Posted by
nahiluhmot on Tuesday June 29, 2021 @08:12PM
from the show-hn dept.
As somebody who uses Dvorak, don't learn an alternative keyboard layout. It makes pair programming, and more generally using other people's computers, an unnecessary pain. More importantly, there are better uses of your time, such as actually programming.
Posted by
nahiluhmot on Thursday March 17, 2016 @10:02AM
from the show-hn dept.
In all fairness, parent's username is shallowpedantic.
Pretty telling that nobody on the set can read Arabic.
I've got a feeling that the Reddit community won't be too keen on this, mostly seeing it as another news organization "stealing" their content. IMO a good way to get users behind this would be to compensate the original posters for their content being posted on Upvoted.
> The BFED realises that while not all experiences will be identical, all browsers can be used to consume a website, even gasp, IE6 and below.
Where would we be if we supported all legacy software? Does there not come a point where cutting support for a class of platforms is a good thing? This article makes some good points, and I think a lot of frontenders (myself included) would benefit from being a bit more "boring", but this article is going a little too far the other way.
Is there any reason that this wouldn't be able to work with another language? If the interface is an HTTP port, it seems like this isn't necessarily tied to Common Lisp.
You have to manually specify the folders you want shared in the arguments to the command. For example, running this:
docker run -v /tmp/:/host-tmp/ ubuntu:14.04 bash -lc "echo 'TEST123' > /host-tmp/test"
Should create a file on your host's filesystem called "/tmp/test" with the text "TEST123".
Great, and I don't want to dismantle the TSA, I just want to have a backdoor to the plane.
> Data persistence support is not out-of-the-box.
This is actually not the case. Although containers do not share any persistent volumes with the host by default, you can use the --volume option[0] to do so.
To answer your question, I've used Docker for local development to run MySQL, Postgres, and Redis inside of containers. Using the aforementioned --volume option, you can share the unix socket opened by either of these services from the container to the host. Otherwise, you can use the --port option[1] to share ports between the container and the host.
I've had a generally pleasant experience using Docker for this use case and would recommend it. It's nice being able to start using a new service by pulling and running an image. Similarly, it's nice to have the ability to clear the state by removing the container, assuming you choose not to mount volumes between the container and the host.
The only frustration I've run into is running out of disk because I have too many images, but it takes a while to get to that point and those can easily be deleted.
[0] https://docs.docker.com/reference/run/#volume-shared-filesys...
[1] https://docs.docker.com/reference/run/#expose-incoming-ports
This is pretty neat. We do our deployment coordination via Slack, and use a listener to parse messages from the channel to see if a delevoper validated their changes. I'm now very tempted to switch that logic to look for emoji reactions.
What makes you think parent is trolling?
Posted by
nahiluhmot on Monday July 06, 2015 @01:39PM
from the reddit.com dept.
I'm really not a fan of the keyword argument feature in Ruby, especially after using ES6 for a good number of projects. It's essentially a special-case of variable destructuring that works for one type of key, Symbols. Also, since its coupled into the arguments of a function, there is no way to use this sort of feature for simple variable assignment.
In addition to slowing the production of money, the URV program essentially tied wages to the inflation rate. To me, that seems like a fundamentally important step in both restoring the people's faith in the currency and maintaining the standard of living for them. By only printing less money, they could easily fall into a period of widespread poverty while inflation rates continued to rise -- albeit at a slower rate.
Of course, I'm just an armchair economist, so perhaps there's part of the picture that I'm not seeing.
I'm curious, do people generally feel that smartwatches are the way of the future? I can't really imagine that a device with a screen the size of a thumbnail outperforming a smartphone for common use cases (scrolling through Twitter, reading emails, browsing the web, etc.) Although at-a-glance notifications and health/sleep tracking are potentially desirable features, it seems that the price will need to drop significantly before anybody besides hobbyists will adopt these.
I can't speak to this framework, but you do not need to use server-side rendering for React applications. Instead, you can essentially serve a blank page on every request, then have the React application bootstrap itself when the page loads. Alternatively, one could precompile the HTML, and serve it as static content with nginx, apache, etc.
I would argue that React is a declarative style as well, the difference between it and the above example being that JS is far more expressive than HTML.
You're part of the post now!
I would argue that neither the person with the most money nor best ideas has the best probability of making more money in this climate. It seems that the person with the most patents now has the greatest probability of making money.
While I agree that patents do enable "the little guy" to succeed in some cases, they also enable the current powers that be to maintain that power.
I would definitely find what curryhoward described as useful, but I don't think Ruby is that language in which it should) be implemented.
That being said, sum types would be a nice addition to this library.
Really cool idea! I like that you can specify a `#respond_to?` constraint instead of a class. Not sure if OP is the author, but here's some feedback:
* It would be better if this didn't pollute the global namespace by defining `#typesig` in `Module` [0] -- perhaps consider refactoring that method into a module which the user may extend. Doing so would also get you out of needing to define `Module#prepend` for older versions of Ruby.
* Perhaps allow the user to enable/disable type checking at a global/class level. For example, then users could only enable type checking during specs if they wanted.
* Instead of using class-level variables, try using class level instance variables. They have less odd behavior when dealing with subclasses [1].
[0] https://github.com/gogotanaka/Rubype/blob/develop/lib/rubype...
[1] http://www.sitepoint.com/class-variables-a-ruby-gotcha/
Edit: Whitespace
I wonder if it costs less in JRuby or if JRuby's version of yield is less optimized.