|
Munkeymon posted:Think it's the other way 'round, technically. Actually, WebStorm might Just Work, but they've got to be having a hard time keeping up with flavors of the week. IntelliJ Ultimate is the full IDE. The minor IDEs like WebStorm, PyCharm are subsets at a lower price point.
|
#
?
Sep 7, 2017 00:17
|
|
|
|
| # ? May 16, 2024 19:59 |
|
|
Echoing VSCode or an IntelliJ IDE.
|
|
#
?
Sep 7, 2017 01:18
|
|
|
Sedro posted:IntelliJ Ultimate is the full IDE. The minor IDEs like WebStorm, PyCharm are subsets at a lower price point. Huh, I was thinking IntelliJ was the 'vanilla' base they added support for other languages to to make all the others.
|
|
#
?
Sep 7, 2017 14:06
|
|
|
Munkeymon posted:Huh, I was thinking IntelliJ was the 'vanilla' base they added support for other languages to to make all the others. It is, in the sense that it doesn't come preconfigured as a polyglot IDE, but all of the JetBrains plugins that comprise the language-specific IDEs are available for download for free if you have the ultimate edition.
|
|
#
?
Sep 7, 2017 14:24
|
|
|
Welp I ended up picking VSCode and I don't regret that one bit. Its fast and light and easy to use, so I'm very happy. Thanks!
|
|
#
?
Sep 7, 2017 14:27
|
|
|
Google came out with a mobile web specialist cert and a study guide for it that's pretty decent: https://developers.google.com/training/certification/mobile-web-specialist/StudyGuide-MobileWebSpecialist.pdf
|
|
#
?
Sep 7, 2017 15:10
|
|
|
FateFree posted:Welp I ended up picking VSCode and I don't regret that one bit. Its fast and light and easy to use, so I'm very happy. Thanks! If I could pry myself from the icy clutches of VIM, I'd pick VS Code.
|
|
#
?
Sep 7, 2017 16:08
|
|
|
Lumpy posted:If I could pry myself from the icy clutches of VIM, I'd pick VS Code. VS Code has a pretty good VIM extension that's worth trying out. Granted, I only used it for the keyboard commands so i might be missing scripts you find necessary. chami fucked around with this message at 17:08 on Sep 7, 2017 |
|
#
?
Sep 7, 2017 17:06
|
|
|
So in a C# .NET environment, I have a link where I want to briefly go to the server to do some quick tasks before doing the actual redirect, but I hate how when you mouseover an <asp:LinkButton> you get "java script:[some gibberish function]". I wanted it to look like a normal href so the user would know what was gonna happen and can open the link in a new window if they want. I ended up doing this:code:
|
|
#
?
Sep 12, 2017 20:56
|
|
|
Tell them what you're going to do in a ToolTip (which I'm assuming generates a title attribute)? If you're whole site is ASP Forms I'm guessing they're used to gibberish links :|
|
|
#
?
Sep 12, 2017 22:00
|
|
|
I wasn't sure to post this here or in the Newbie Programmer/Get A Job thread, but I figured you embittered grizzled veterans would give me better hot takes to trot out than there. I have an interview tomorrow with an SaaS provider who's been going for several years, and then was acquired by a bigger company a couple years ago. The position is not specifically programming, but reading between the lines the only reason they contacted me was because of my programming experience. The idea is that I'd take new customers on the platform and integrate them and their processes within it; my guess is with a heavy dose of ETL/Database trickery, starting and herding feature pulls with the development team, and basically programming my own solutions as required in whatever format I'd wish (non-core, data manip tools only). I'm clear on that, I'm a database manipulatin mofo of long experience, and they have no expectations of me knowing their base platforms/technologies. But I thought it'd be good to impress in the interview. These are the technologies they claim their backbone is built on, I've organized them into categories: Things I have no idea what they are Sidekiq - An update of the cool contact manager from Borland?? Redis/ElasticSearch - Looks like kind of like Lucene/SOLR for those weird noSQL databases that all the kids use these days? Things I kinda know what it is but have never used: Rails - Web app specific MVC framework for the Ruby language Engines - A way to pretend you've made your Rails app easy to use by others Mongoid - An ORM (sorry... ODM) for those weird noSQL databases that all the cool kids use these days Things I definitely know what they are but have never used: MongoDB - noSQL "document" oriented database that weirdos use Hadoop - Data processing framework when you have a lot of things in your MongoDB for weirdos install I'm not expecting you guys to learn me everything about these technologies, but hopefully help me avoid basic pitfalls and assumptions about them. For example (unlike many recruiters apparently) I know that "Rails" isn't a programming language, despite not knowing a word of Ruby. If you have any tips/insights into the other technologies like that that could make me appear to have at least a surface comprehension of the other stuff I've listed I'd greatly appreciate it!
|
|
#
?
Sep 13, 2017 04:30
|
|
|
ElasticSearch is basically magic Lucene for JSON. It does fulltext searching for arbitrary (but consistently structured) documents. That is, it does well if each document entered into a search index has the same structure, but you can define as many document types as you need. It automatically figures out what to index, but you can give it hints. You can even use it as a primary data store but that would be a horrifyingly bizarre thing to do. Redis is basically disk-persisted memcached, with arrays ("lists") and hashes as first class data structures. Any other use than as a cache is batshit insanity. Both have clustering abilities that make them a pleasure to develop with but a hypothetical nightmare to manage. Sidekiq seems to be a background processing module for Ruby. Oh also all the cool kids realized that Mongo is horrible about three years ago. It has a use case, and that use case is if your data never ever needs joins, but I'm sure you already know this. Given the job description, you might be talking to one of the few cases where Mongo might actually be a good choice. That might be interesting.
|
|
#
?
Sep 13, 2017 07:42
|
|
|
Is there a reason for me not to use Angular 2.0 over Angular 1.X for a new project? It's the typical web frontend for a dedicated API back end, nothing amazingly fancy, plenty of custom validation and widgets required, though I'd prefer not to spend all my time reinventing the wheel so decent third party library support for the usual suspects would be nice. I would look into react.js or some of the other frameworks but we mostly use angular in-house and I'd prefer to keep it in the family as it were.
|
|
#
?
Sep 13, 2017 11:08
|
|
|
CapnAndy posted:So in a C# .NET environment, I have a link where I want to briefly go to the server to do some quick tasks before doing the actual redirect, but I hate how when you mouseover an <asp:LinkButton> you get "java script:[some gibberish function]". I wanted it to look like a normal href so the user would know what was gonna happen and can open the link in a new window if they want. I ended up doing this: Ugh, ASP.NET server side rendering. FWIW most new development with a C# back end these days uses it for an API and only and handles the javascript, html, css on the client instead of going through MSFT's retarded training-wheels-for-VB6 model.
|
|
#
?
Sep 13, 2017 11:52
|
|
|
NtotheTC posted:Is there a reason for me not to use Angular 2.0 over Angular 1.X for a new project? It's the typical web frontend for a dedicated API back end, nothing amazingly fancy, plenty of custom validation and widgets required, though I'd prefer not to spend all my time reinventing the wheel so decent third party library support for the usual suspects would be nice. I would look into react.js or some of the other frameworks but we mostly use angular in-house and I'd prefer to keep it in the family as it were. Angular 1.x and 2+ are very different, but if you can swing it I highly suggest angular 2+, it's less painful to work with overall, and you avoid $scope hell.
|
|
#
?
Sep 13, 2017 12:35
|
|
|
TheCog posted:Angular 1.x and 2+ are very different, but if you can swing it I highly suggest angular 2+, it's less painful to work with overall, and you avoid $scope hell. Or do even better and skip Angular altogether and just use ReactJS
|
|
#
?
Sep 13, 2017 13:33
|
|
|
ModeSix posted:Or do even better and skip Angular altogether and just use ReactJS I did specify keeping it in the angular family  What's the compelling argument for ReactJS over Angular?TheCog posted:Angular 1.x and 2+ are very different, but if you can swing it I highly suggest angular 2+, it's less painful to work with overall, and you avoid $scope hell. Thanks, I'll go with 2+ then. I've used typescript with angular 1.x in the past and enjoyed it so while different it should be an improvement.
|
|
#
?
Sep 13, 2017 13:40
|
|
|
NtotheTC posted:I did specify keeping it in the angular family Having used both AngularJS and ReactJS, I find that React is lighter weight. It's less opinionated, in that the core functionality of it is solely the View aspect of MVC. You will need to know what 3rd party libraries to use with it, but the ecosystem is quite great. React uses a component based system (like Angular), but it doesn't force you into it's opinionated way of doing things as Angular tends to do. You have the choice of using X or Y or even 123 library with it to give it the functionality that's build directly into Angular. You can extend the functionality as you see fit, and only how you see fit. People will argue in favour of one or the other, and I guess it comes to personal opinion on which way is best. I used Angular 1.x and I tried to transition to Angular 2.x and just couldn't get my head around it, whereas going to ReactJS felt much more simple. Take this with a grain of salt, because it's just my amateur opinion. 
|
|
#
?
Sep 13, 2017 16:43
|
|
|
ModeSix posted:Having used both AngularJS and ReactJS, I find that React is lighter weight. It's less opinionated, in that the core functionality of it is solely the View aspect of MVC. You will need to know what 3rd party libraries to use with it, but the ecosystem is quite great. More simply put, Angular is a puzzle , while React is a piece of the puzzle 
|
|
#
?
Sep 13, 2017 17:44
|
|
|
I feel like its kind of an arbitrary distinction. I mean, you can add on all sorts of stuff to Angular too. Anyway, even if we go with the distinction, there's a huge difference between React and a lot of other libraries...there are well-established community guidelines for how to wire React up to well-established other libraries that are meant to go with it. It's almost as if you can view the community conventions around React as the framework.
|
|
#
?
Sep 13, 2017 17:55
|
|
|
IAmKale posted:That's exactly the point of using a framework like Angular vs a library like React: the framework includes a lot more functionality because it's supposed to be a platform upon which you can build something without having to incorporate a lot of third-party libraries. A library like React, though, is intended to be paired with other libraries until you have compiled a collection suitable for use as a framework. Well I'm glad I "get it" then. As I said though, it's just my personal amateur opinion.
|
|
#
?
Sep 13, 2017 18:03
|
|
|
I feel like Angular has way more in common with React than it does something like EmberJS, which is what I'd hold up as an example of a JS Framework.
|
|
#
?
Sep 13, 2017 18:24
|
|
|
Thermopyle posted:I feel like its kind of an arbitrary distinction. I mean, you can add on all sorts of stuff to Angular too. All of this is made moot by the fact that everything now has a command line tool. I absolutely adore this trend because it means I can get a project up and running with an opinionated (and probably better) Webpack setup, PWA support, suitable AJAX and routing support...it's magic 
|
|
#
?
Sep 13, 2017 19:35
|
|
|
Maybe a distinction I should make is that I primarily use React Native rather than ReactJS. They're essentially the same thing, but with mobile specific things built in. The cognate in Angular is a loving mess. Ionic I think?
|
|
#
?
Sep 13, 2017 19:46
|
|
|
IAmKale posted:Oh no doubt, I'm not denying this at all. The image I've been keeping in my head is that while, out of the box, Angular would let you create a functioning SPA with AJAX support and routing, React would require you to wire up a library for routing, axios for AJAX, etc... before you had just as capable a setup. Yeah, I wasn't trying to disagree with you, just adding to the conversation. I have a hard time getting on board with the command line tools. Not because I don't think they're good and useful its just that I usually want to do things slightly differently plus I usually have a project skeleton that I can just copy/paste so they don't save me much time anyway. I do keep trying to get myself to use them (well, mainly create-react-app), I just tend to fall back to my old way of doing it.
|
|
#
?
Sep 13, 2017 19:48
|
|
|
ModeSix posted:Maybe a distinction I should make is that I primarily use React Native rather than ReactJS. They're essentially the same thing, but with mobile specific things built in. I'm not sure they are directly comparable since Ionic still is a webapp in a browser (cordova) shell. Ionic 2+ is real nice though, the upgrade to Angular 2 (and Typescript) helped a ton.
|
|
#
?
Sep 13, 2017 21:00
|
|
|
gmq posted:I'm not sure they are directly comparable since Ionic still is a webapp in a browser (cordova) shell. I work with ionic 3, and it's a mix of nice and wtf every day. Like for example, recently we discovered that http requests sent with the native http method on our Android build would automatically parse javascript objects into JSON if you used them as the body parameter. In the iOS build, it would instead send undefined if you didn't first parse the JavaScript object into JSON yourself.
|
|
#
?
Sep 13, 2017 21:12
|
|
|
TheCog posted:I work with ionic 3, and it's a mix of nice and wtf every day. Like for example, recently we discovered that http requests sent with the native http method on our Android build would automatically parse javascript objects into JSON if you used them as the body parameter. In the iOS build, it would instead send undefined if you didn't first parse the JavaScript object into JSON yourself. If by native you mean it's a Cordova plugin, yeah, they are very hit or miss. The camera preview one has the weirdest bugs and I have to use it in two different projects. 
|
|
#
?
Sep 13, 2017 21:20
|
|
|
McGlockenshire posted:ElasticSearch is basically magic Lucene for JSON. It does fulltext searching for arbitrary (but consistently structured) documents. That is, it does well if each document entered into a search index has the same structure, but you can define as many document types as you need. It automatically figures out what to index, but you can give it hints. You can even use it as a primary data store but that would be a horrifyingly bizarre thing to do. Thanks buddy! Heading out to the interview now
|
|
#
?
Sep 13, 2017 22:32
|
|
|
gmq posted:I'm not sure they are directly comparable since Ionic still is a webapp in a browser (cordova) shell. That's true, they aren't exactly the same. RN is far better if you were to ask me, because it's really easy to reach out and touch the native API and functions of a device using a single code base.
|
|
#
?
Sep 13, 2017 23:14
|
|
|
Grump posted:I have a <a></a> that by default is unclickable I dunno about a purely CSS solution, but you could do something like this: https://jsfiddle.net/6ztL2wrr/
|
|
#
?
Sep 14, 2017 02:40
|
|
|
ModeSix posted:The cognate in Angular is a loving mess. Ionic I think? If you are talking native apps, the comparison is NativeScript, which we've been using for a few months now after ditching Ionic. I like it a lot more than Ionic, but there's always some bad with the good when you are dealing with a multi-platform mobile tool. I love how easy it is to directly use the native APIs though.
|
|
#
?
Sep 14, 2017 15:22
|
|
|
DICTATOR OF FUNK posted:I dunno about a purely CSS solution, but you could do something like this: https://jsfiddle.net/6ztL2wrr/ yeah I ended up just adding and removing a class and that worked 
|
|
#
?
Sep 14, 2017 16:06
|
|
|
Hey y'all. I finally got around to parsing this big ol' xml file for my Electron/pouchdb project. The user selects the file and then I read it using fs. This works on a small test xml doc but crashes on my 8.6MB xml file. I'm imagining there's some file size or memory limits happening somewhere? It's loading a local file so I naively thought it would just work and not be so size dependent. Any ideas would be appreciated. I tried both the sync and async ways of loading using fs:code:code:
|
|
#
?
Sep 14, 2017 20:20
|
|
|
What do you mean by "crash"?
|
|
#
?
Sep 14, 2017 22:27
|
|
|
Okay my bad. Chrome dev tools was crashing cause i was trying to output the whole thing to the console. I believe it is working just fine.
|
|
#
?
Sep 14, 2017 23:51
|
|
|
So Vue. Its nice. I find myself getting stuck in the component mentality when trying to utilize UI frameworks. I've been used to Bootstrap but that relies on JQuery so I've looked at all the pretty vue UI frameworks like Vuetify, Element, Quasar etc. It really seems like a barrier to entry that every framework has its own set of components that I need to learn an API for, and customizing things becomes much more of a hassle. Maybe I'm going about this wrong. In the prototyping phase, should I just pick a regular, non-vue framework and make my own set of components just for quicker development? And then maybe swap out the guts when I'm ready to make it nice? The only problem is now I feel like I'm creating a whole set of components like buttons and alerts blah blah. It seems tricky to customize and prototype at the same time. Now I'm going back and forth with which UI framework to stick with, since it seems like such a commitment to have to learn everything. Maybe I should base everything off a regular CSS framework like Material Lite, and make my own components out of that? I'd appreciate any guidance.
|
|
#
?
Sep 15, 2017 17:35
|
|
|
I have an upcoming project with a central component that relies on an external API. The backend of the site is WordPress (at the client's request), but I can do pretty much whatever I want on the frontend. I'm curious if anyone has any helpful PHP/JS tools/frameworks they've used previously and would recommend specifically with regards to requesting/caching data from the API? I've worked with lots of APIs previously so I'm not totally ignorant, but I haven't worked on a project where the API was the cornerstone of the project. Thus I want to make sure I don't code something that's going to blow up too easily. I'm still learning and not quite ready to start using React on client projects, unfortunately.
|
|
#
?
Sep 20, 2017 15:26
|
|
|
Critique thread in CC is archived, I hope it's ok to ask for design advice here instead. It accepts a use input list of genres, and a distance from the user's location and it returns a list of venues (or bands) that match that genre and distance. So this below is the search feature with some user input:  What main design changes should I make? Sleepy Robot fucked around with this message at 20:15 on Sep 20, 2017 |
|
#
?
Sep 20, 2017 18:55
|
|
|
|
| # ? May 16, 2024 19:59 |
|
|
kedo posted:I have an upcoming project with a central component that relies on an external API. The backend of the site is WordPress (at the client's request), but I can do pretty much whatever I want on the frontend. I'm curious if anyone has any helpful PHP/JS tools/frameworks they've used previously and would recommend specifically with regards to requesting/caching data from the API? I've worked with lots of APIs previously so I'm not totally ignorant, but I haven't worked on a project where the API was the cornerstone of the project. Thus I want to make sure I don't code something that's going to blow up too easily. That's an interesting question actually. There's tons of info about frameworks to build APIs but not a whole lot about actually using them. The last time I did I kind of gutted out something in Slim but that was a while ago and I have no idea if they're still around/updating.
|
|
#
?
Sep 20, 2017 19:39
|
|