I have been working on an internal, form-heavy, app for a bank client for the past 6 months as my day job. I wouldn’t say I love Angular 2/4/5, but it does get the job done. Since Angular has a rather steep learning curve, having someone who has experience with it on the team will help avoid a lot of headaches and gotchas.
There are certainly some issues with Angular. For example, starting Webpack Dev Server is really slow (a minute or longer). Running a lot of tests with Kharma can be slow. If you know what the issues are and can either live with or work around them, then it is not that bad.
To make a child element the same height as the parent, you can set the parent container to position: relative, and in the child element, set it to position: absolute; top: 0; bottom: 0. The downside of this trick is that the child element is now absolutely positioned and no longer behaves the same. Alternatively, you can use flexbox to do this, if using it is an option.
My favorite use of this is making a resizable box that always maintains the same aspect ratio. Padding % is out of the element's width. So width: 100%, padding-top: 50% will make a block that is 2:1 that resizes automatically.
I am hoping JetBrains folks will port their suite of .Net tools to other platforms. Since the core of these tools is already cross platform (JVM-based), it may happen faster than Microsoft does to Visual Studio.
Most of the JetBrains products won't be relevant when Roslyn ships. Visual Studio 2015 already ships with many ReSharper features out of the box, with the ability to add the missing ones being made trivial by the new Roslyn APIs.
I definitely won't be running ReSharper in VS 2015.
I’ve been doing the same—building a fairly large content-based website with around 100 pages for a telecom using Middleman. The site will be live soon, and I hope to be able to share more info about it when that happens.
So far, what I can tell is that Middleman provides a more efficient workflow than the database-driven CMSes I have used in the past.
Great list. I agree with most of these conventions, except the following:
> List "Regular" Styles Next
> List @include(s) Next
Depends on what the @include gives you, I would either treat @include the same as @extend and put @include after @extend, or just treat @include as regular styles and mix them together. The reason for this is that I generally organize my styles by listing block styles first and then the text styles. It would mess up this organization if all @includes that set only 1 property are listed the last.
I assume you mean having the book physically shipped to Sri Lanka is not feasible/possible. Consider buying the ebook from Manning directly [0]. They do offer the ebook in Kindle (mobi) format.
Once there's a pdf or other ebook available it'll be pirated. How that doesn't damage sales I'll never understand.
The Lazarus (object pascal ide) book is only available in a physical book format for this reason.
In another life I wrote technical books, which at the time were only available in physical formats. That didn't stop electronic versions of the more popular books from appearing on usenet.
That's a good read. It's hard to understand the motivation of someone who's prepared to put in that many hours pirating a single book. It's seems a bit pathetic
I agree that it bothers me to see Gitlab UI looking too similar to GitHub. I’m hoping that GitHub would not pursue any action against it. I also agree that Gitlab can’t compete against GitHub in the areas you’ve listed.
For my company, however, Gitlab makes a lot of sense. We have a large number of small and close source client projects to manage. We don’t want to pay for file hosting, e.g. $50 a month for 50 repos, when each repo is tiny and we can easily and cheaply host them. GitHub Enterprise is also out of question, as it is not very affordable by a small company.
Cost factor aside, Gitlab does have advantages over GitHub. Legal requirement is one, and the ability to integrate with other tools in the company is also quite nice. Although this feature has not been implemented yet, I look forward to the ability for Gitlab to integrate with Jenkins and display build status.
I will continue to use GitHub for personal and open source projects. For client work, Gitlab will be the one I use.
Just installed Gitlab successfully on RHEL6. Some modifications to the installation steps:
- I used RVM to install Ruby 1.9.3. This should be fairly straightforward.
- adduser command has a different interface on RHEL, but it shouldn’t be hard to figure out.
- I used Apache ProxyPass instead of Nginx. unicorn.rb needed to be updated to listen on a tcp port instead of a socket file.
- Supplied init.d script did not work out of box. Some modifications were required.
- Redis server was installed from REMI.
Let me know where you’re stuck and I can try to help you.
I agree that Gitlab is not very easy to install, as there are many complicated steps. The benefits of having a free private GitHub, though, were totally worth it.
There are certainly some issues with Angular. For example, starting Webpack Dev Server is really slow (a minute or longer). Running a lot of tests with Kharma can be slow. If you know what the issues are and can either live with or work around them, then it is not that bad.