jdiscar

> So movie theater > movie at home for most people.

I'm really wonder if that's true for most people. Sure, there are people that would rather watch in the theater, but there are also people who'd rather hold a hardcover to read.

Would you want to look at them again but forget or are you just bookmarking out of habit?

I tried to solve this with my app Mochimarks, best used through the Chrome Extension: https://chrome.google.com/webstore/detail/mochimarks-chrome-...

For "todo list", marking something as Read Later works perfectly. Lots of bookmarks app do this and it's most convenient to view them by creation date.

For reminders, Mochimarks lets you set explicit reminders on every bookmark or note. The notifications can be viewed in the app, show up through the extension, and are emailed to you. You can snooze the alerts too.

I have a concept to add a feature to track if something has changed on the site since the last time you visited, but it's not implemented.

Mochimarks has a rest api. It has lots of sorting options too (creation, last visited, total visits, interest, and reminders.) It's made bookmarks a lot more useful for me.

I thought about this a lot... so this'll be long. I thought of how bookmarks were used and came up with:

- Things you want easy access to, but have annoying URLs, like your company's wiki page (Solved by Favorites/Bookmarks Bar or Dashboard)

- Things you want to finish looking at later (Solved by Read Later / Reminder)

- Things you want to keep track of, like blogs (Solved by Read Later / Reminder)

- Things you want to be able to find later (Solved by Full Text Search and Tags)

- Something you might want to see again, but not anytime soon (Solved by Personal Archive)

- Something you simply liked or are favoriting (Solved by Personal Archive)

- Note taking / Research (Solved by Tags and Boards)

- Idea inspiration (Solved by Tags and Boards)

- Things you want to show other people (Solved by Social)

- Things you want to get for yourself (Solved by Wishlist)

- Things you want other people to get for you (Solved by Wishlist)

My main problem with using bookmarks was that I rarely went back to them. Normal bookmarks are essentially a personal archive and google search usually finds things much better.

I realized there were a lot of bookmarks I'd like to go back to, I'd just forget about them. Maybe I'd like to read something when I got home from work, or maybe I wanted to check back in a week for an update (or release date), or I wanted to keep a list of items to show someone later (usually funny videos or gifs.) It was pretty difficult to do that no matter how I organized my folders or tagged things.

I eventually built my own bookmark site (https://www.mochimarks.com/landing) with all the features I wanted. The main features (apart from the expected tagging/full text search/browser integration/notes/etc...) were settable/automatic reminders, wishlists, and recommendations. Wishlists let you rank bookmarks. Recommendations could be new stuff from friends or the app could recommend that you look at stuff you liked that you hadn't visited in a while.

After having my app for a while, I've found I use bookmarks a lot more. I mostly use reminders and have a few stuff pop up to check each day. Reminders are killer for me. But when I'm bored I like to sort my wishlists. I don't use tags much... I really only use #Programming, #Interesting (usually really good articles), #Funny, #Music, #Blog, and #ArtBlog. I'll use the recommendation features to check on my blogs and to share links with my friends. I use Read Later a lot, but rarely actually go back and read things later. But when I do, I'm really glad the feature is there.

I've been working on a bookmarking app with a feature that reminds you to revisit bookmarks (either algorithmically or manually via a schedule.) It also has built-in wishlisting and a bunch of other stuff I always wanted out of a bookmark app. Bookmark apps are a really crowded space and I have no idea how to advertise something with so many alternatives, I built this app because I always wanted these features I couldn't find elsewhere.

https://www.mochimarks.com/landing

I use a paper notebook to sketch out diagrams and sometimes make todo lists. I like to use the notebook during useful meetings too, I feel like it's less distracting than a computer.

Thanks for checking it out and thanks a lot of the feedback! There is a suggest tags system in place right now, but it relies on crowd sourcing and there aren't many users right now. I've considered doing some statistical analysis, but I've been focusing on other features first.

I plan to charge once I'm done with the beta, but it would be more of a side business. It started out as a toy though, so who knows what'll happen long term.

Yeah, the guide is kind of hidden away at https://mochimarks.com/info/api

If you use the "suggestion" sorting, it will recommend some links it thinks you should look at again. It bases this on several factors, like the interest level, tags, creation date, last visited date, and last modified date. It does a lot of time decay. I'm still tuning the algorithm, so it should improve as time goes on.

Hi, creator here. I made Mochimarks because I found that recently, I wanted to go back to certain links at certain times. For example, I'd want to go back to a kickstarter on the day it was ending. Since I resolved to make an online bookmark app anyway, I decided to make my dream bookmark app and add a bunch of features I'd always wanted to have. My focus is to make bookmarks more actively useful. While there's more stuff I want to do, Mochimarks is ready for beta and I would really appreciate some feedback.

Mochimarks has configurable reminders, wishlisting, bookmark ranking, opt-in sharing, and can recommend bookmarks it thinks you might want to read again. Mochimarks also has the features you'd expect from an modern bookmarking website, including tags, read later, full text search, responsive design, and lots of sorting options. I've tried hard to pay close attention to security and privacy. I'm still working on batch editing bookmarks.

The easiest way to interact with Mochimarks is via its chrome extension. Otherwise, there are bookmarklets. I know the online bookmark space is crowded, but I've personally found the features I've added really useful. Thanks!

I think there should be a point to address running out of memory. If you just keep adding images/animation/videos, eventually the site experience will be bad.

In this case, it might be easier to describe sending letters in a secret code to your friends. Even though the mailmen can read everything on the envelope, they can't read anything inside.

I think this is fine. Java is verbose as it is, it would be even worse if Exceptions were handled "as intended" and every Exception type was treated individually. Log and move on can be appropriate in some cases. And even if 80% of the time you're ignoring all Exceptions, the 20% of the time you have specific code could be very, very important.

This article was about what stack to use for a startup and reddit is certainly no longer a startup. Tech stacks definitely change to adapt to its needs, at some point a company should be trying out cutting edge stuff. But the stack a 100 person company is capable of maintaining is very different than what a 3 person company can handle.

I think this is really great advice. This mindset was critical for me to finally start finishing up my side projects. For me, working by myself, 'Choose the tech I know best' is more applicable (although that generally happens to be the boring tech anyway.) But 'stick to the boring tech' is probably much better if you need to eventually start hiring employees. In my experience, technology stacks change drastically as a company gets bigger.

That said, as always, YMMV. Using cutting edge technology certainly has its place. There's just a learning and maintenance curve to account for that can often get in the way of releasing and running your MVP. But if you've taken that into account, it could be fine for your startup.

For me, it's all about discipline. You don't delete your interests, you just force yourself to focus on the thing you've decided is most important. Sometimes you need a break or have 'writer's block' and can play with some other interests, but at the end of the day, you need to finish the thing you've prioritized.

There's nothing wrong with having lots of interests and playing around with lots of pet projects. But the more you do that, the less likely you'll ever finish anything. There's certainly a lot of sacrifice in order to see something to completion.

It's because it's a pretty situational thing to talk about. IMO, the most sensible reasons to move away from RDS would be customer requirements or you're not using AWS for anything else.

What traits are you comparing on? What kind of a thing are you building? What features (cost, performance, ease of use, time) are the most important to you?

At what scale have you found Performance and Size Limitations an issue? I've seen people leave due to cost before (not that I thought they were always correct), but not for the other two you listed.

Yeah, VARCHAR and TEXT are backed by the same datatype, but VARCHAR(N) gives you a limit check (that can be a pain to change if you ever need to.) There shouldn't be any noticable performance difference. For UUIDs, the native type is way better.

Are you saying a NoSQL solution is better for this use case? Because that's what this article is asking. Sure, they could do things better (can't we always?), but that's not the point they're trying to make.

Like you said, 10GB of data isn't very much, it really doesn't matter if you go with NoSQL or SQL. But SQL will probably give you more flexibility and will be easier to manage until you get really, really big.

The point of this article is showing how MySQL could be used to get a lot of what a NoSQL solution provides. NoSQL certainly has a place, but a lot of people don't really understand what that is and simply use NoSQL because it's popular, which cuts them off from a lot of useful features a SQL solution could provide them. That said, you're right more care could have been put in the details of the article, but a lot of the points could be correct for their situation.

For example, 'Do not normalize.'

This was in the context of a read heavy table that competes with NoSQL. In that context, I think this is accurate. We noticed a big difference after denormalizing when we went from millions of rows to billions of rows.

The general advice of SQL solutions being as useful as NoSQL to a certain scale is good. I don't think the individual examples are horrible, but they aren't universal advice to achieve NoSQL performance.

It's really up to what kind of project you want to work on and how much resources (time/effort/stress/money/etc..) you want to put into it. The learning curve for something new is definitely not negligible, especially as you get deep into your project.

Newer languages/frameworks look great when you run through tutorials, but you're going to have issues once you need to do more complicated stuff. Very new frameworks are unlikely to have much documentation and discussions, which means that at some point, you're probably going to need cross your fingers and hope someone replies to your questions or dig into source code yourself. There's nothing wrong with this, it's just the cost of using something that isn't old and popular.

Maintainability for large projects and bad performance are an issue in whatever language or framework you use. A lot of the problems are avoidable once you move past relying on the magic of your web framework and understand how all the stuff you're using works under the covers. After playing with a few languages and frameworks, I'd say it's really useful to just choose one to become an expert in. Being an expert in one and knowing how to mitigate all the warts will help you infinitely when you do eventually move to something new. I think it's much more valuable to be an expert in one stack and intermediate in two than to be intermediate in 20 stacks.

If you have something you really want to build and are already comfortable with Java, I'd suggest just sticking with Java. Newer frameworks like SpringBoot or Play! remove a lot of the XML, if that's your primary complaint. Verbosity... well, every language is going to have something that doesn't match your personal aesthetics. A lot of the really verbose Java can be avoided by changing up your coding style.

If you're just going for self-enrichment, sticking with an FP until you're comfortable with it is great. Just be aware that you may never use the language/framework as an employee. But you'll definitely get huge benefits in your overall skills by learning an FP.

If you haven't seen hacker koans, they're fun to read through. Sure they're largely parody, but some of the popular ones feel like proper koans.

The rails stack isn't designed for Windows, why should they waste dev cycles trying to support it? In any case, I do a fair amount of webdev on my windows gaming computer (don't want to mix work and side projects), VMs are so easy to set up that I barely install any dev tools on base os.