Badger looks promising, though I'm not database-expert enough to know when to choose LSM tree database. (BoltDB is B tree, and Badger is LSM tree with value log.)
I use Evernote rather than bookmark, which you get organized with nothing but folder structuring. It's totally hard to manage, validate, and find when you want to.
Evernote, on the other hand, provides a creative means: taking a note on your own way. By creating a Notebook and a Note, you can give a brief statement of the linked articles, which could come in useful for later full-text search.
Longform Podcast entertains me with a variety of guests, who is typically a writer, a editor, or a journalist, invited for each episodes. With dialogues about their work and career, it gives a glimpse of a life of those who work in the media industry. The podcast is a oral history of media workers, and it often gives valuable insights to just listen to interviews and see interviewees as they are.
Facing challenges like fake news, Google AMP, FaceBook InstantArticle, and the like, some of you may be interested.
I guess that the main benefit of GitHub Marketplace would be the full-scale integration with GitHub Issue and Project board, launched last year. Consider a common situation: when CI fails, people need to reopen an issue manually, getting an error report via email. People who are in charge of project management may be seeking a better way to streamline the manual task, which probably increased since the introduction of Project board.
To be clear, I’ve been away from software development over the years, so I’m curious about the impact of Project board. Does it useful in the first place? Did it require manual tasks between other services such as CI? Do you, who is in charge of issue or board assignment, feel frustration using it?
I want Apple News and Instant Article to join in AMP so that media developers could reduce the cost of news distribution following the single standard. I even want crawling services, Feedly or Pocket, to serve AMP with advertisements so that I could support writers, journalists and media companies; besides, I have no idea if web feed, RSS or Atom, could consume AMP.
Google, which would gain the most benefit from AMP, deserves criticism for potential abuse of their power. Online media, which serve pages with poor performance, deserve criticism for its reluctance to improve their poor UX. AMP, however, hardly deserves criticism, through a perspective of user experience and news distribution.
AMP may look intimidating to the open web philosophy, be tepid approach from a technological point of view. But we need more experiment as it stands: everyone can become a media with the Web, old media is still playing a valuable role in society, online media lack prospects for the future to be profitable enough to invest in journalism. Fighting for the open web is good, but fighting for it without caring about anyone but technological principle is no good.
One of the features I like is default parameters. I'd like to add a usage that isn't mentioned in the article. It's really handy to pass optional parameters since default parameters can be nested.
class Hoge {
foo({active=true, collapsed=false, silent=false}={}) {
}
}
let hoge = new Hoge();
hoge.foo({collapsed: true});
In the blog article above, they mentioned a problem they faced.
> The docs were built around Hugo, which is not natively supported by GitHub, and took minutes to build, and even longer for us to deploy.
I've been using Middleman for static site for a couple of years. I'm thinking about moving to Hugo because I read HN comments Hugo is much faster than other alternatives. But reading the official Docker blog, I'm thinking twice.
Could anyone tell me the reason why Docker blog took too much time to build with Hugo that is supposed to build really fast?
I'm using feedly.com for reading tech blogs. For long articles, I use getpocket.com to read it later instead of Feedly's 'Read it later' feature.
Both service give me the hints of popularity of the article. Pocket adds 'Best Of' label for popular articles. Feedly adds a number of 'Read it later'.
I'm currently using Feedly for subscribing podcasts. But it's not handy to use. If RadioPublic give me the same feature that feedly and pocket provide for the sake of podcast listening, I'll definitely use the service.
I'd quote an interesting point of view on MBA from Joi Ito's TED talk.
Before the Internet, if you remember, when we tried to create services, what you would do is you'd create the hardware layer and the network layer and the software and it would cost millions of dollars to do anything that was substantial. So when it costs millions of dollars to do something substantial, what you would do is you'd get an MBA who would write a plan and get the money from V.C.s or big companies, and then you'd hire the designers and the engineers, and they'd build the thing. This is the Before Internet, B.I., innovation model.
Badger looks promising, though I'm not database-expert enough to know when to choose LSM tree database. (BoltDB is B tree, and Badger is LSM tree with value log.)